Security Deep Dive
netmaker
Security posture and CVE patch evidence from tracked releases.
2 critical dependency CVEs affects v1.5.1.
Audit transitive dependencies; consider upgrading or pinning replacements.
Trust Signals — 3 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
3d stale
scorecard
1.76 / 4.0
Score 4.4/10
cve health
0.00 / 2.5
⚠ No direct scan — 2c/3h 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.40 / 10.0
Risk 14.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
8.6
10%
Provenance trust
provenance trust
4.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 14.0/100Scorecard
Scorecard 4.4/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10 |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | 8 | Found 9/11 approved changesets -- score normalized to 8 |
| Security-Policy | 10 | security policy file detected |
| Fuzzing | 0 | project is not fuzzed |
| License | 9 | license file detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Dangerous-Workflow | 0 | dangerous workflow patterns detected |
| Packaging | 10 | packaging workflow detected |
| Branch-Protection | 6 | branch protection is not maximal on development and all release branches |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
| 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
2
High
3
Medium
1
Low
2
Unknown
2
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-33186 | critical | — | google.golang.org/grpc | v1.79.2 | — |
| CVE-2026-33816 | critical | — | github.com/jackc/pgx/v5 | v5.7.2 | — |
| CVE-2026-29181 | high | — | go.opentelemetry.io/otel | v1.39.0 | — |
| CVE-2026-34986 | high | — | github.com/go-jose/go-jose/v3 | v3.0.3 | — |
| CVE-2026-34986 | high | — | github.com/go-jose/go-jose/v4 | v4.1.3 | — |
| CVE-2025-27144 | medium | — | github.com/go-jose/go-jose/v3 | v3.0.3 | — |
| CVE-2026-26958 | low | — | filippo.io/edwards25519 | v1.1.0 | — |
| CVE-2026-41889 | low | — | github.com/jackc/pgx/v5 | v5.7.2 | — |
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.52.0 | — |
| CVE-2026-33815 | unknown | — | github.com/jackc/pgx/v5 | v5.7.2 | — |
Showing 10 of 10