Security Deep Dive
cerbos
Security posture and CVE patch evidence from tracked releases.
6 high-severity dependency CVEs affects v0.53.0.
Review the dependency vulnerabilities below.
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
1d stale
scorecard
2.64 / 4.0
Score 6.6/10
cve health
0.25 / 2.5
⚠ No direct scan — 0c/6h 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.23 / 10.0
Risk 12.3/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
1.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
8.8
10%
Provenance trust
provenance trust
6.6
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 12.3/100Scorecard
Scorecard 6.6/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 | 10 | all changesets reviewed |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Fuzzing | 0 | project is not fuzzed |
| Pinned-Dependencies | 9 | dependency not pinned by hash detected -- score normalized to 9 |
| License | 10 | license file detected |
| 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 |
| Security-Policy | 0 | security policy file not detected |
| Packaging | 10 | packaging workflow detected |
| Signed-Releases | 8 | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| SAST | 2 | SAST tool is not run on all commits -- score normalized to 2 |
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
6
Medium
4
Low
1
Unknown
1
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-26996 | high | — | minimatch | 7.4.6 | — |
| CVE-2026-27903 | high | — | minimatch | 7.4.6 | — |
| CVE-2026-27904 | high | — | minimatch | 7.4.6 | — |
| CVE-2026-4800 | high | — | lodash | 4.17.21 | — |
| CVE-2026-6321 | high | — | fast-uri | 3.1.0 | — |
| CVE-2026-6322 | high | — | fast-uri | 3.1.0 | — |
| CVE-2024-24786 | medium | — | google.golang.org/protobuf | 1.27.1 | — |
| CVE-2025-13465 | medium | — | lodash | 4.17.21 | — |
| CVE-2025-69873 | medium | — | ajv | 8.17.1 | — |
| CVE-2026-2950 | medium | — | lodash | 4.17.21 | — |
| CVE-2026-41889 | low | — | github.com/jackc/pgx/v4 | v4.18.3 | — |
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.51.0 | — |
Showing 12 of 12