Skip to content
Tools / kopia / Security

Security Deep Dive

kopia

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 high-severity dependency CVEs affects v0.23.0.

Review the dependency vulnerabilities below.

✓ Signed ✗ SLSA — SBOM ✗ Security policy Weekly cadence · 6d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present
Signed releases Present
Latest release artifact signature Sigstore
Last verified: 15d ago
SLSA provenance Absent
Attestation predicate level Latest release
Last verified: 15d ago
SBOM published Unknown
GitHub SBOM API Latest release
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 21d ago
Release cadence: weekly Present
6d median over recent releases Release history
Latest release: 23d ago
Maintainer active Present
Recent commit activity Repository
Last commit: today
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 23d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 23d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 23d ago
7.5/10 Security Score
6.8/10 Scorecard
Dependency Exposure 3 transitive dependency CVEs found in the latest SBOM.

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

Up to date

scorecard

2.72 / 4.0

Score 6.8/10

cve health

2.00 / 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.48 / 10.0

Risk 4.8/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

8.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

9.5

10%

supply chain risk: 4.77 transitive cves: 0c/2h

Provenance trust

provenance trust

6.8

40%

scorecard score: 6.8 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none
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 4.8/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
61% Dependency freshness

Scorecard

Scorecard 6.8/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check Score Reason
Maintained 10 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Packaging -1 packaging workflow not detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Code-Review 6 Found 9/14 approved changesets -- score normalized to 6
Dependency-Update-Tool 10 update tool detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
Binary-Artifacts 10 no binaries found in the repo
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies 7 dependency not pinned by hash detected -- score normalized to 7
Signed-Releases 8 5 out of the last 5 releases have a total of 5 signed artifacts.
Fuzzing 0 project is not fuzzed
Security-Policy 0 security policy file not detected
Branch-Protection 4 branch protection is not maximal on development and all release branches
Vulnerabilities 8 2 existing vulnerabilities detected
SAST 10 SAST tool is run on all commits
License 10 license file detected
CI-Tests 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Contributors 10 project has 9 contributing companies or organizations

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

594 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

0

High

2

Medium

1

Low

0

Unknown

0

High 2 Medium 1
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-6321 high fast-uri 3.1.0 v0.23.0
CVE-2026-6322 high fast-uri 3.1.0 v0.23.0
CVE-2026-42338 medium ip-address 10.1.0 v0.23.0

Showing 3 of 3

Beta — feedback welcome: [email protected]