Security Deep Dive
Maddy Mail Server
Security posture and CVE patch evidence from tracked releases.
No known vulnerabilities in v0.9.5.
1 CVE patched in tracked history. Median patch time: 0 days.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| v0.9.5 | 2026-05-23 | — | — | — | — | — |
Latest
|
| v0.9.4 | 2026-04-30 | — | — | — | — | — |
—
|
| v0.9.3 | 2026-04-12 | — | — | — | — | — |
Patches
GHSA-5835-4gvc-32pc
|
| v0.9.2 | 2026-03-26 | — | 1 | — | — | — |
—
|
| v0.9.1 | 2026-03-26 | — | 1 | — | — | — |
—
|
| v0.9.0 | 2026-03-25 | — | 1 | — | — | — |
—
|
| v0.8.2 | 2026-01-14 | — | 1 | — | — | — |
—
|
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
Security Score
A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.
epss
0.25 / 0.5
No EPSS data
freshness
1.00 / 1.0
8d stale
scorecard
2.08 / 4.0
Score 5.2/10
cve health
2.50 / 2.5
No open CVEs
patch speed
0.50 / 0.5
0d avg
kev exposure
1.50 / 1.5
No KEV exposure
supply chain risk
0.00 / 10.0
Risk 0.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
10.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
10.0
10%
Provenance trust
provenance trust
5.2
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
8.5
10%
How is this calculated?
The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.
Scorecard
Scorecard 5.2/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10 |
| Security-Policy | 4 | security policy file detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Code-Review | 2 | Found 6/24 approved changesets -- score normalized to 2 |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Packaging | 10 | packaging workflow detected |
| Signed-Releases | 8 | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 3 | branch protection is not maximal on development and all release branches |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
CVE Patch History
Median patch time: 0 daysTracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.
CVEs Patched by Year
| CVE | Severity | EPSS | Disclosed | Fixed in | Days to fix | vs Ecosystem Median | KEV |
|---|---|---|---|---|---|---|---|
| GHSA-5835-4gvc-32pc | High | — | — | v0.9.3 | — | — | — |
KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.