# Dependency vulnerability email template

> Explore this dependency vulnerability email template for technology and software. Preview its status, three key details, and next action.

Source: https://design.moosewave.com/templates/dependency-vulnerability-email-template/

---

Transactional Alerts & status

# Dependency vulnerability email template

A third-party library flaw disclosed with the actual exposure assessed.
Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.
**Best for**
: A third-party library flaw disclosed with the actual exposure assessed
**Structure**
: State or event context · Plain-language explanation · Three labelled facts
**Style**
: letter · display mix
**Industry fit**
: Technology & software
Responsive design preview

## See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.
Want to change the copy and style?

## Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.
Message anatomy

## A useful starting point, with the important parts named.

Scanners flag the library rather than the usage. We searched the codebase for every call site and found none in the vulnerable path.

### What you can change

- Brand name
- Subject line
- Preheader
- Eyebrow
- Headline
- Supporting copy
- Primary action label
- Primary action URL

### What to keep clear

- State or event context
- Plain-language explanation
- Three labelled facts
- Primary and secondary action
- Support or privacy footer
Complete starting copy

## Read it as text, not only as a picture.

**From**
: Swanwick Alerts
**Subject**
: A library we use has a flaw, and you are not exposed
**Preheader**
: We do not use the affected function. Here is how we checked.
Vulnerability

### The flaw is real and the affected function is one we never call

Scanners flag the library rather than the usage. We searched the codebase for every call site and found none in the vulnerable path.

#### Severity

High, in the library

#### Our exposure

None found

#### Patched anyway

Today
Moosewave MCP

## Give an agent the structure, the job, and a stopping point.

The brief asks for a new draft and stops before send.

**Read the complete brief**
Connected work

## Take the design beyond the canvas.

Keep exploring

## Related transactional templates

[001 Transactional Open preview ↗ Alerts & status Anomaly detected Unusual activity flagged with the reasoning shown Technology & software](/templates/anomaly-detected-email-template/)
[002 Transactional Open preview ↗ Alerts & status Battery backup exhausted A power protection device that can no longer hold a load Technology & software](/templates/battery-backup-exhausted-email-template/)
[003 Transactional Open preview ↗ Alerts & status Data is stale A dashboard showing old figures, flagged before decisions are made on it Technology & software](/templates/data-is-stale-email-template/)
[004 Transactional Open preview ↗ Alerts & status Disk nearly full A storage warning with the specific thing consuming the space Technology & software](/templates/disk-nearly-full-email-template/)