Skip to content
Tools / writefreely / Security

Security Deep Dive

writefreely

Security posture and CVE patch evidence from tracked releases.

Back to Tool

9 critical dependency CVEs affects v0.17.1.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✓ Security policy Dormant cadence · 162d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present
Signed releases Unknown
Latest release artifact signature Latest release
—
SLSA provenance Unknown
Attestation predicate level Latest release
—
SBOM published Unknown
GitHub SBOM API Latest release
—
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 8d ago
Release cadence: dormant Present
162d median over recent releases Release history
Latest release: 6d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 8d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 6d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 6d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 6d ago
4.0/10 Security Score
5.7/10 Scorecard
Dependency Exposure 73 transitive dependency CVEs found in the latest SBOM. 9 critical.

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

1d stale

scorecard

2.28 / 4.0

Score 5.7/10

cve health

0.00 / 2.5

⚠ No direct scan — 9c/34h 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.50 / 10.0

Risk 100.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

0.0

10%

supply chain risk: 100.0 transitive cves: 9c/34h

Provenance trust

provenance trust

5.7

40%

scorecard score: 5.7 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

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 100.0/100
9 Transitive critical CVEs
0 KEV-transitive CVEs
69% Dependency freshness

Scorecard

Scorecard 5.7/10

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

Check Score Reason
Code-Review 0 Found 0/11 approved changesets -- score normalized to 0
Maintained 10 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Security-Policy 10 security policy file detected
Token-Permissions 9 detected GitHub workflow tokens with excessive permissions
Dangerous-Workflow 10 no dangerous workflow patterns detected
Binary-Artifacts 10 no binaries found in the repo
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
License 10 license file detected
Signed-Releases 0 Project has not signed or included provenance with any releases.
Fuzzing 0 project is not fuzzed
SAST 0 SAST tool is not run on all commits -- score normalized to 0
Branch-Protection -1 internal error: error during GetBranch(main) error during branchesHandler.query: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
Packaging 10 packaging workflow detected

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

741 dependencies scanned View full dependency list →

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

Critical

9

High

34

Medium

20

Low

9

Unknown

1

Still affecting latest (3) All (73)
Critical 9 High 34 Medium 20 Low 9 Unknown 1
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2021-44906 critical — minimist 0.0.8 v0.17.0
CVE-2022-37601 critical — loader-utils 1.4.0 v0.17.0
CVE-2023-45133 critical — @babel/traverse 7.11.5 v0.17.0
CVE-2023-45133 critical — babel-traverse 6.26.0 v0.17.0
CVE-2025-6545 critical — pbkdf2 3.0.17 v0.17.0
CVE-2025-6547 critical — pbkdf2 3.0.17 v0.17.0
CVE-2025-9287 critical — cipher-base 1.0.4 v0.17.0
CVE-2025-9288 critical — sha.js 2.4.11 v0.17.0
GHSA-vjh7-7g9h-fjfh critical — elliptic 6.5.2 v0.17.0
CVE-2020-13822 high — elliptic 6.5.2 v0.17.0
CVE-2020-7660 high — serialize-javascript 2.1.2 v0.17.0
CVE-2020-7774 high — y18n 4.0.0 v0.17.0
CVE-2020-7788 high — ini 1.3.5 v0.17.0
CVE-2020-8203 high — lodash 4.17.15 v0.17.0
CVE-2021-23337 high — lodash 4.17.20 v0.17.0
CVE-2021-27290 high — ssri 6.0.1 v0.17.0
CVE-2021-32803 high — tar 4.4.13 v0.17.0
CVE-2021-32804 high — tar 4.4.13 v0.17.0
CVE-2021-37701 high — tar 4.4.13 v0.17.0
CVE-2021-37712 high — tar 4.4.13 v0.17.0
CVE-2021-37713 high — tar 4.4.13 v0.17.0
CVE-2021-3807 high — ansi-regex 4.1.0 v0.17.0
CVE-2022-25858 high — terser 4.6.6 v0.17.0
CVE-2022-25883 high — semver 7.0.0 v0.17.0
CVE-2022-3517 high — minimatch 3.0.4 v0.17.0
CVE-2022-37599 high — loader-utils 1.4.0 v0.17.0
CVE-2022-37603 high — loader-utils 1.4.0 v0.17.0
CVE-2022-38900 high — decode-uri-component 0.2.0 v0.17.0
CVE-2022-46175 high — json5 1.0.1 v0.17.0
CVE-2023-46234 high — browserify-sign 4.0.4 v0.17.0
CVE-2024-21538 high — cross-spawn 6.0.5 v0.17.0
CVE-2024-4068 high — braces 2.3.2 v0.17.0
CVE-2026-23745 high — tar 4.4.13 v0.17.0
CVE-2026-23950 high — tar 4.4.13 v0.17.0
CVE-2026-24842 high — tar 4.4.13 v0.17.0
CVE-2026-26960 high — tar 4.4.13 v0.17.0
CVE-2026-26996 high — minimatch 3.0.4 v0.17.0
CVE-2026-27903 high — minimatch 3.0.4 v0.17.0
CVE-2026-27904 high — minimatch 3.0.4 v0.17.0
CVE-2026-29786 high — tar 4.4.13 v0.17.0
CVE-2026-31802 high — tar 4.4.13 v0.17.0
CVE-2026-4800 high — lodash 4.17.20 v0.17.0
GHSA-5c6j-r48x-rmvq high — serialize-javascript 2.1.2 v0.17.0
CVE-2020-15366 medium — ajv 6.12.0 v0.17.0
CVE-2020-28498 medium — elliptic 6.5.2 v0.17.0
CVE-2020-28500 medium — lodash 4.17.20 v0.17.0
CVE-2020-7598 medium — minimist 0.0.8 v0.17.0
CVE-2020-7608 medium — yargs-parser 13.1.1 v0.17.0
CVE-2021-23343 medium — path-parse 1.0.6 v0.17.0
CVE-2021-23364 medium — browserslist 4.14.1 v0.17.0
CVE-2022-21670 medium — markdown-it 12.0.4 v0.17.0
CVE-2024-28863 medium — tar 4.4.13 v0.17.0
CVE-2024-4067 medium — micromatch 3.1.10 v0.17.0
CVE-2025-13465 medium — lodash 4.17.20 v0.17.0
CVE-2025-24358 medium — github.com/gorilla/csrf v1.7.2 v0.17.0
CVE-2025-27789 medium — @babel/runtime 7.11.2 v0.17.0
CVE-2025-27789 medium — @babel/helpers 7.8.4 v0.17.0
CVE-2025-47909 medium — github.com/gorilla/csrf v1.7.2 v0.17.0
CVE-2025-69873 medium — ajv 6.12.0 v0.17.0
CVE-2026-2739 medium — bn.js 4.11.8 v0.17.0
CVE-2026-2950 medium — lodash 4.17.20 v0.17.0
CVE-2026-33750 medium — brace-expansion 1.1.11 v0.17.0
CVE-2026-34043 medium — serialize-javascript 2.1.2 v0.17.0
CVE-2017-16137 low — debug 4.1.1 v0.17.0
CVE-2024-42459 low — elliptic 6.5.2 v0.17.0
CVE-2024-42460 low — elliptic 6.5.2 v0.17.0
CVE-2024-42461 low — elliptic 6.5.2 v0.17.0
CVE-2024-48948 low — elliptic 6.5.2 v0.17.0
CVE-2024-48949 low — elliptic 6.5.2 v0.17.0
CVE-2025-14505 low — elliptic 6.5.2 v0.17.0
CVE-2025-5889 low — brace-expansion 1.1.11 v0.17.0
CVE-2026-26958 low — filippo.io/edwards25519 v1.1.0 v0.17.0
CVE-2026-33814 unknown — golang.org/x/net v0.51.0 v0.17.0

Showing 73 of 73

Beta — feedback welcome: [email protected]