Security Deep Dive
opensnitch
Security posture and CVE patch evidence from tracked releases.
1 actively-exploited dependency CVE affects v1.8.0.
KEV-listed CVEs are confirmed exploited in the wild — patch urgently.
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
0.95 / 1.0
47d stale
scorecard
1.92 / 4.0
Score 4.8/10
cve health
0.00 / 2.5
⚠ No direct scan — 1c/12h 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 43.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.7
10%
Provenance trust
provenance trust
4.8
40%
Maintainer health
maintainer health
9.5
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 43.0/100Scorecard
Scorecard 4.8/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Code-Review | 5 | Found 6/12 approved changesets -- score normalized to 5 |
| 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 |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Pinned-Dependencies | 2 | dependency not pinned by hash detected -- score normalized to 2 |
| Security-Policy | 0 | security policy file not detected |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Branch-Protection | 0 | branch protection not enabled on development/release branches |
| Signed-Releases | 8 | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| 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
1
High
12
Medium
11
Low
0
Unknown
7
1 dependency vulnerabilities are in KEV.
CISA confirmed these vulnerabilities are actively exploited. Treat as critical priority.
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-33186 | critical | — | google.golang.org/grpc | 1.32.0 | — |
| CVE-2015-5237 | high | — | protobuf | — | — |
| CVE-2019-9512 | high | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2021-33194 | high | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2021-38561 | high | — | golang.org/x/text | 0.3.0 | — |
| CVE-2022-1941 | high | — | protobuf | — | — |
| CVE-2022-27664 | high | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2022-32149 | high | — | golang.org/x/text | 0.3.0 | — |
| CVE-2022-41723 | high | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2023-39325 | high | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2025-4565 | high | — | protobuf | — | — |
| CVE-2026-0994 | high | — | protobuf | — | — |
| GHSA-m425-mq94-257g | high | — | google.golang.org/grpc | 1.32.0 | — |
| CVE-2020-14040 | medium | — | golang.org/x/text | 0.3.0 | — |
| CVE-2021-31525 | medium | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2022-29526 | medium | — | golang.org/x/sys | 0.0.0-20190606203320-7fc4e5ec1444 | — |
| CVE-2022-41717 | medium | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2023-3978 | medium | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2023-44487 | medium | KEV | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2023-45288 | medium | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2024-24786 | medium | — | google.golang.org/protobuf | 1.26.0 | — |
| CVE-2024-45339 | medium | — | github.com/golang/glog | 0.0.0-20160126235308-23def4e6c14b | — |
| CVE-2025-22870 | medium | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2025-22872 | medium | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2021-22570 | unknown | — | protobuf | — | — |
| CVE-2021-44716 | unknown | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2024-45338 | unknown | — | golang.org/x/net | 0.0.0-20190311183353-d8887717615a | — |
| CVE-2025-47911 | unknown | — | golang.org/x/net | 0.38.0 | — |
| CVE-2025-58190 | unknown | — | golang.org/x/net | 0.38.0 | — |
| CVE-2026-33814 | unknown | — | golang.org/x/net | 0.38.0 | — |
| GO-2023-2153 | unknown | — | google.golang.org/grpc | 1.32.0 | — |
Showing 31 of 31