Security Deep Dive
Sensu
Security posture and CVE patch evidence from tracked releases.
1 actively-exploited dependency CVE affects v6.14.1.
KEV-listed CVEs are confirmed exploited in the wild — patch urgently.
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
1d stale
scorecard
1.80 / 4.0
Score 4.5/10
cve health
0.00 / 2.5
⚠ No direct scan — 3c/8h 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.5
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 43.0/100Scorecard
Scorecard 4.5/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 4 | 0 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 4 |
| Packaging | -1 | packaging workflow not detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Code-Review | 8 | Found 10/12 approved changesets -- score normalized to 8 |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0 | security policy file not detected |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Binary-Artifacts | 10 | no binaries found in the repo |
| License | 10 | license file detected |
| Fuzzing | 0 | project is not fuzzed |
| 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 |
| Signed-Releases | -1 | no releases found |
| 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
3
High
8
Medium
13
Low
2
Unknown
8
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-2024-45337 | critical | — | golang.org/x/crypto | 0.3.0 | — |
| CVE-2026-33186 | critical | — | google.golang.org/grpc | 1.41.0 | — |
| CVE-2026-33816 | critical | — | github.com/jackc/pgx/v5 | 5.1.1 | — |
| CVE-2020-26160 | high | — | github.com/dgrijalva/jwt-go | 3.2.0+incompatible | — |
| CVE-2023-39325 | high | — | golang.org/x/net | 0.7.0 | — |
| CVE-2024-27304 | high | — | github.com/jackc/pgx/v5 | 5.1.1 | — |
| CVE-2025-22869 | high | — | golang.org/x/crypto | 0.3.0 | — |
| CVE-2025-30204 | high | — | github.com/golang-jwt/jwt/v4 | 4.4.2 | — |
| CVE-2025-3445 | high | — | github.com/mholt/archiver/v3 | 3.3.1-0.20191129193105-44285f7ed244 | — |
| CVE-2025-65637 | high | — | github.com/sirupsen/logrus | 1.9.0 | — |
| GHSA-m425-mq94-257g | high | — | google.golang.org/grpc | 1.41.0 | — |
| CVE-2023-3978 | medium | — | golang.org/x/net | 0.7.0 | — |
| CVE-2023-44487 | medium | KEV | golang.org/x/net | 0.7.0 | — |
| CVE-2023-45288 | medium | — | golang.org/x/net | 0.7.0 | — |
| CVE-2023-48795 | medium | — | golang.org/x/crypto | 0.3.0 | — |
| CVE-2024-0406 | medium | — | github.com/mholt/archiver/v3 | 3.3.1-0.20191129193105-44285f7ed244 | — |
| CVE-2024-24786 | medium | — | google.golang.org/protobuf | 1.27.1 | — |
| CVE-2025-11579 | medium | — | github.com/nwaples/rardecode | 1.0.0 | — |
| CVE-2025-22870 | medium | — | golang.org/x/net | 0.7.0 | — |
| CVE-2025-22872 | medium | — | golang.org/x/net | 0.7.0 | — |
| CVE-2025-47914 | medium | — | golang.org/x/crypto | 0.3.0 | — |
| CVE-2025-58058 | medium | — | github.com/ulikunitz/xz | 0.5.10 | — |
| CVE-2025-58181 | medium | — | golang.org/x/crypto | 0.3.0 | — |
| GHSA-fqpg-rq76-99pq | medium | — | github.com/jackc/pgx/v5 | 5.1.1 | — |
| CVE-2024-51744 | low | — | github.com/golang-jwt/jwt/v4 | 4.4.2 | — |
| CVE-2026-41889 | low | — | github.com/jackc/pgx/v5 | 5.1.1 | — |
| CVE-2024-45338 | unknown | — | golang.org/x/net | 0.7.0 | — |
| CVE-2025-47911 | unknown | — | golang.org/x/net | 0.7.0 | — |
| CVE-2025-47913 | unknown | — | golang.org/x/crypto | 0.3.0 | — |
| CVE-2025-58190 | unknown | — | golang.org/x/net | 0.7.0 | — |
| CVE-2026-33814 | unknown | — | golang.org/x/net | 0.7.0 | — |
| CVE-2026-33815 | unknown | — | github.com/jackc/pgx/v5 | 5.1.1 | — |
| GO-2023-2153 | unknown | — | google.golang.org/grpc | 1.41.0 | — |
| GO-2024-2567 | unknown | — | github.com/jackc/pgx/v5 | 5.1.1 | — |
Showing 34 of 34