Security Deep Dive
podsync
Security posture and CVE patch evidence from tracked releases.
1 high-severity dependency CVE affects v2.8.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
6d stale
scorecard
2.04 / 4.0
Score 5.1/10
cve health
2.25 / 2.5
No open 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.20 / 10.0
Risk 2.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
9.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
9.8
10%
Provenance trust
provenance trust
5.1
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.0/100Scorecard
Scorecard 5.1/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 0 | Found 0/10 approved changesets -- score normalized to 0 |
| Maintained | 10 | 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Token-Permissions | 7 | 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 |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Branch-Protection | 1 | branch protection is not maximal on development and all release branches |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Packaging | 10 | packaging workflow detected |
| SAST | 10 | SAST tool is run on all commits |
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
0
Low
0
Unknown
2
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2025-30204 | high | — | github.com/golang-jwt/jwt | v3.2.2+incompatible | — |
| CVE-2020-8911 | unknown | — | github.com/aws/aws-sdk-go | v1.44.144 | — |
| CVE-2020-8912 | unknown | — | github.com/aws/aws-sdk-go | v1.44.144 | — |
Showing 3 of 3