Security Deep Dive
papermerge
Security posture and CVE patch evidence from tracked releases.
6 critical dependency CVEs affects 3.5.3.
Audit transitive dependencies; consider upgrading or pinning replacements.
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
0.52 / 1.0
192d stale
scorecard
1.12 / 4.0
Score 2.8/10
cve health
0.00 / 2.5
No open CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
1.50 / 1.5
No KEV exposure
supply chain risk
-1.50 / 10.0
Risk 58.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
4.2
10%
Provenance trust
provenance trust
2.8
40%
Maintainer health
maintainer health
5.2
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.
Supply Chain Risk
Risk 58.0/100Scorecard
Scorecard 2.8/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 0 | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Code-Review | 0 | Found 0/30 approved changesets -- score normalized to 0 |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10 | no binaries found in the repo |
| SAST | 0 | no SAST tool detected |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0 | security policy file not detected |
| Packaging | -1 | packaging workflow not detected |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Signed-Releases | -1 | no releases found |
| Branch-Protection | 0 | branch protection not enabled on development/release branches |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
6
High
17
Medium
10
Low
0
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2021-35042 | critical | — | django | 3.2 | — |
| CVE-2022-28346 | critical | — | django | 3.2 | — |
| CVE-2022-28347 | critical | — | django | 3.2 | — |
| CVE-2022-34265 | critical | — | django | 3.2 | — |
| CVE-2023-31047 | critical | — | django | 3.2 | — |
| CVE-2025-64459 | critical | — | django | 3.2 | — |
| CVE-2021-23727 | high | — | celery | — | — |
| CVE-2021-31542 | high | — | django | 3.2 | — |
| CVE-2021-33571 | high | — | django | 3.2 | — |
| CVE-2021-45115 | high | — | django | 3.2 | — |
| CVE-2021-45116 | high | — | django | 3.2 | — |
| CVE-2022-2255 | high | — | mod-wsgi | — | — |
| CVE-2022-23833 | high | — | django | 3.2 | — |
| CVE-2022-36359 | high | — | django | 3.2 | — |
| CVE-2022-41323 | high | — | django | 3.2 | — |
| CVE-2023-23969 | high | — | django | 3.2 | — |
| CVE-2023-24580 | high | — | django | 3.2 | — |
| CVE-2023-36053 | high | — | django | 3.2 | — |
| CVE-2023-43665 | high | — | django | 3.2 | — |
| CVE-2023-46695 | high | — | django | 3.2 | — |
| CVE-2024-24680 | high | — | django | 3.2 | — |
| CVE-2025-57833 | high | — | django | 3.2 | — |
| CVE-2025-64458 | high | — | django | 3.2 | — |
| CVE-2011-4356 | medium | — | celery | — | — |
| CVE-2021-32052 | medium | — | django | 3.2 | — |
| CVE-2021-33203 | medium | — | django | 3.2 | — |
| CVE-2021-44420 | medium | — | django | 3.2 | — |
| CVE-2021-45452 | medium | — | django | 3.2 | — |
| CVE-2022-22818 | medium | — | django | 3.2 | — |
| CVE-2023-41164 | medium | — | django | 3.2 | — |
| CVE-2024-27351 | medium | — | django | 3.2 | — |
| CVE-2024-45231 | medium | — | django | 3.2 | — |
| CVE-2025-48432 | medium | — | django | 3.2 | — |
Showing 33 of 33