Security Deep Dive
Netcap
Security posture and CVE patch evidence from tracked releases.
1 high-severity dependency CVE affects v0.9.0.
Review the dependency vulnerabilities below.
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
11d stale
scorecard
1.36 / 4.0
Score 3.4/10
cve health
1.00 / 2.5
⚠ No direct scan — 0c/1h 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
-0.29 / 10.0
Risk 2.9/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
4.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
9.7
10%
Provenance trust
provenance trust
3.4
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 2.9/100Scorecard
Scorecard 3.4/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Packaging | -1 | packaging workflow not detected |
| Maintained | 10 | 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10 |
| Code-Review | 0 | Found 0/30 approved changesets -- score normalized to 0 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns 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 |
| SAST | 0 | no SAST tool detected |
| Security-Policy | 0 | security policy file not detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| License | 10 | license file detected |
| Fuzzing | 0 | project is not fuzzed |
| Branch-Protection | 0 | branch protection not enabled on development/release branches |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- 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
0
High
1
Medium
5
Low
1
Unknown
3
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-27606 | high | — | rollup | 4.53.3 | — |
| CVE-2022-31022 | medium | — | github.com/blevesearch/bleve | v1.0.14 | — |
| CVE-2026-33532 | medium | — | yaml | 1.10.2 | — |
| CVE-2026-33809 | medium | — | golang.org/x/image | v0.25.0 | — |
| CVE-2026-41305 | medium | — | postcss | 8.5.8 | — |
| CVE-2026-41506 | medium | — | github.com/go-git/go-git/v5 | v5.17.2 | — |
| CVE-2024-53384 | low | — | tsup | 8.0.0 | — |
| CVE-2026-33812 | unknown | — | golang.org/x/image | v0.25.0 | — |
| CVE-2026-33813 | unknown | — | golang.org/x/image | v0.25.0 | — |
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.51.0 | — |
Showing 10 of 10