Skip to content
Tools / projectsend / Security

Security Deep Dive

projectsend

Security posture and CVE patch evidence from tracked releases.

Back to Tool

5 high-severity dependency CVEs affects r2029.

Review the dependency vulnerabilities below.

✗ Signed ✗ SLSA ✓ SBOM ✓ Security policy Weekly cadence · 6d median Active maintainer

Trust Signals — 4 of 9 Present

Evidence already collected from releases and repository metadata.

4/9 Present
Signed releases Absent
Latest release artifact signature None
Last verified: 5d ago
SLSA provenance Absent
Attestation predicate level Latest release
Last verified: 5d ago
SBOM published Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 17d ago
Release cadence: weekly Present
6d median over recent releases Release history
Latest release: 2mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 13d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 2mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 2mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 2mo ago
4.2/10 Security Score
4.3/10 Scorecard
Dependency Exposure 33 transitive dependency CVEs found in the latest SBOM.

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

12d stale

scorecard

1.72 / 4.0

Score 4.3/10

cve health

0.25 / 2.5

⚠ No direct scan — 0c/5h transitive 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.05 / 10.0

Risk 10.5/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

1.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

9.0

10%

supply chain risk: 10.46 transitive cves: 0c/5h

Provenance trust

provenance trust

4.3

40%

scorecard score: 4.3 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 12d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none
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 10.5/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
77% Dependency freshness

Scorecard

Scorecard 4.3/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check Score Reason
Code-Review 0 Found 0/21 approved changesets -- score normalized to 0
Maintained 10 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Security-Policy 9 security policy file detected
Packaging -1 packaging workflow not detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Binary-Artifacts 10 no binaries found in the repo
Pinned-Dependencies 3 dependency not pinned by hash detected -- score normalized to 3
License 10 license file detected
Fuzzing 0 project is not fuzzed
Signed-Releases 0 Project has not signed or included provenance with any releases.
Branch-Protection 1 branch protection is not maximal on development and all release branches
SAST 0 SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

411 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

0

High

5

Medium

25

Low

3

Unknown

0

High 5 Medium 25 Low 3
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-42033 high axios 1.15.0
CVE-2026-42035 high axios 1.15.0
CVE-2026-42043 high axios 1.15.0
CVE-2026-42264 high axios 1.15.0
CVE-2026-4800 high lodash-es 4.17.21
CVE-2023-44270 medium postcss 7.0.39
CVE-2025-13465 medium lodash-es 4.17.21
CVE-2025-15599 medium dompurify 2.5.8
CVE-2025-26791 medium dompurify 2.5.8
CVE-2026-0540 medium dompurify 2.5.8
CVE-2026-28343 medium @ckeditor/ckeditor5-html-support 44.3.0
CVE-2026-28343 medium ckeditor5 44.3.0
CVE-2026-2950 medium lodash-es 4.17.21
CVE-2026-33532 medium yaml 1.10.2
CVE-2026-41239 medium dompurify 2.5.8
CVE-2026-41240 medium dompurify 2.5.8
CVE-2026-41305 medium postcss 7.0.39
CVE-2026-42034 medium axios 1.15.0
CVE-2026-42036 medium axios 1.15.0
CVE-2026-42037 medium axios 1.15.0
CVE-2026-42038 medium axios 1.15.0
CVE-2026-42039 medium axios 1.15.0
CVE-2026-42041 medium axios 1.15.0
CVE-2026-42042 medium axios 1.15.0
CVE-2026-42044 medium axios 1.15.0
GHSA-39q2-94rc-95cp medium dompurify 2.5.8
GHSA-cj63-jhhr-wcxv medium dompurify 2.5.8
GHSA-cjmm-f4jc-qw8r medium dompurify 2.5.8
GHSA-h8r8-wccr-v5f2 medium dompurify 2.5.8
GHSA-r4q5-vmmm-2653 medium follow-redirects 1.15.11
CVE-2025-58064 low @ckeditor/ckeditor5-clipboard 44.3.0
CVE-2025-58064 low ckeditor5 44.3.0
CVE-2026-42040 low axios 1.15.0

Showing 33 of 33

Beta — feedback welcome: [email protected]