Security Deep Dive
server
Security posture and CVE patch evidence from tracked releases.
2 critical dependency CVEs affects v2.9.1.
Audit transitive dependencies; consider upgrading or pinning replacements.
Trust Signals — 4 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
4d stale
scorecard
2.00 / 4.0
Score 5.0/10
cve health
0.00 / 2.5
Open CVEs detected
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 48.8/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.1
10%
Provenance trust
provenance trust
5.0
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.
Supply Chain Risk
Risk 48.8/100Scorecard
Scorecard 5.0/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Maintained | 10 | 30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | -1 | packaging workflow not detected |
| Code-Review | 5 | Found 3/6 approved changesets -- score normalized to 5 |
| Security-Policy | 10 | security policy file detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| License | 9 | license file detected |
| Fuzzing | 0 | project is not fuzzed |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Branch-Protection | -1 | internal error: error during branchesHandler.setup: 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 |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
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
2
High
20
Medium
20
Low
3
Unknown
2
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-27699 | critical | — | basic-ftp | 5.1.0 | — |
| CVE-2026-33816 | critical | — | github.com/jackc/pgx/v5 | v5.7.6 | — |
| CVE-2026-25547 | high | — | @isaacs/brace-expansion | 5.0.0 | — |
| CVE-2026-26996 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-27606 | high | — | rollup | 4.57.1 | — |
| CVE-2026-27903 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-27904 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-29181 | high | — | go.opentelemetry.io/otel | v1.40.0 | — |
| CVE-2026-32141 | high | — | flatted | 3.3.3 | — |
| CVE-2026-33228 | high | — | flatted | 3.3.3 | — |
| CVE-2026-33671 | high | — | picomatch | 4.0.3 | — |
| CVE-2026-34986 | high | — | github.com/go-jose/go-jose/v4 | v4.0.5 | — |
| CVE-2026-39363 | high | — | vite | 7.3.1 | — |
| CVE-2026-39364 | high | — | vite | 7.3.1 | — |
| CVE-2026-41324 | high | — | basic-ftp | 5.1.0 | — |
| CVE-2026-42033 | high | — | axios | 1.13.6 | — |
| CVE-2026-42035 | high | — | axios | 1.13.6 | — |
| CVE-2026-42043 | high | — | axios | 1.13.6 | — |
| CVE-2026-42264 | high | — | axios | 1.13.6 | — |
| CVE-2026-44240 | high | — | basic-ftp | 5.1.0 | — |
| CVE-2026-4800 | high | — | lodash | 4.17.21 | — |
| GHSA-6v7q-wjvx-w8wg | high | — | basic-ftp | 5.1.0 | — |
| CVE-2025-13465 | medium | — | lodash | 4.17.21 | — |
| CVE-2025-62718 | medium | — | axios | 1.13.6 | — |
| CVE-2025-66400 | medium | — | mdast-util-to-hast | 13.2.0 | — |
| CVE-2026-2950 | medium | — | lodash | 4.17.21 | — |
| CVE-2026-33532 | medium | — | yaml | 1.10.2 | — |
| CVE-2026-33672 | medium | — | picomatch | 4.0.3 | — |
| CVE-2026-33750 | medium | — | brace-expansion | 2.0.2 | — |
| CVE-2026-39365 | medium | — | vite | 7.3.1 | — |
| CVE-2026-40175 | medium | — | axios | 1.13.6 | — |
| CVE-2026-41305 | medium | — | postcss | 8.5.6 | — |
| CVE-2026-42034 | medium | — | axios | 1.13.6 | — |
| CVE-2026-42036 | medium | — | axios | 1.13.6 | — |
| CVE-2026-42037 | medium | — | axios | 1.13.6 | — |
| CVE-2026-42038 | medium | — | axios | 1.13.6 | — |
| CVE-2026-42039 | medium | — | axios | 1.13.6 | — |
| CVE-2026-42041 | medium | — | axios | 1.13.6 | — |
| CVE-2026-42042 | medium | — | axios | 1.13.6 | — |
| CVE-2026-42044 | medium | — | axios | 1.13.6 | — |
| CVE-2026-42338 | medium | — | ip-address | 10.1.0 | — |
| GHSA-r4q5-vmmm-2653 | medium | — | follow-redirects | 1.15.11 | — |
| CVE-2026-26958 | low | — | filippo.io/edwards25519 | v1.1.0 | — |
| CVE-2026-41889 | low | — | github.com/jackc/pgx/v5 | v5.7.6 | — |
| CVE-2026-42040 | low | — | axios | 1.13.6 | — |
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.51.0 | — |
| CVE-2026-33815 | unknown | — | github.com/jackc/pgx/v5 | v5.7.6 | — |
Showing 47 of 47