Skip to content
Tools / Perkeep / Security

Security Deep Dive

Perkeep

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v0.12.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA ✓ SBOM ✗ Security policy Unknown cadence Sporadic maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/9 Present
Signed releases Unknown
Latest release artifact signature Latest release
SLSA provenance Unknown
Attestation predicate level Latest release
SBOM published Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 18d ago
Release cadence Unknown
12-release median Release history
Latest release: 6mo ago
Maintainer sporadic Present
Recent commit activity Repository
Last commit: 4mo ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 6mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 6mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 6mo ago
4.7/10 Security Score
3.5/10 Scorecard
Dependency Exposure 13 transitive dependency CVEs found in the latest SBOM. 1 critical.

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.72 / 1.0

122d stale

scorecard

1.40 / 4.0

Score 3.5/10

cve health

0.75 / 2.5

⚠ No direct scan — 1c/0h 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

-0.40 / 10.0

Risk 4.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

3.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

9.6

10%

supply chain risk: 4.0 transitive cves: 1c/0h

Provenance trust

provenance trust

3.5

40%

scorecard score: 3.5 openssf badge: none

Maintainer health

maintainer health

7.3

10%

activity freshness: 122d

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.0/100
1 Transitive critical CVEs
0 KEV-transitive CVEs
100% Dependency freshness

Scorecard

Scorecard 3.5/10

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

Check Score Reason
Code-Review 3 Found 10/27 approved changesets -- score normalized to 3
Maintained 0 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow 10 no dangerous workflow patterns detected
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 9 binaries present in source code
Security-Policy 0 security policy file not detected
License 10 license file detected
Signed-Releases 0 Project has not signed or included provenance with any releases.
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
Fuzzing 0 project is not fuzzed
Packaging 10 packaging workflow detected
SAST 0 SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies 1 dependency not pinned by hash detected -- score normalized to 1

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

135 dependencies scanned View full dependency list →

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

Critical

1

High

0

Medium

3

Low

1

Unknown

8

Critical 1 Medium 3 Low 1 Unknown 8
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-33186 critical google.golang.org/grpc v1.59.0
CVE-2025-47914 medium golang.org/x/crypto v0.38.0
CVE-2025-58181 medium golang.org/x/crypto v0.38.0
CVE-2026-33809 medium golang.org/x/image v0.27.0
CVE-2026-26958 low filippo.io/edwards25519 v1.1.0
CVE-2020-8911 unknown github.com/aws/aws-sdk-go v1.44.51
CVE-2020-8912 unknown github.com/aws/aws-sdk-go v1.44.51
CVE-2025-47911 unknown golang.org/x/net v0.40.0
CVE-2025-47913 unknown golang.org/x/crypto v0.38.0
CVE-2025-58190 unknown golang.org/x/net v0.40.0
CVE-2026-33812 unknown golang.org/x/image v0.27.0
CVE-2026-33813 unknown golang.org/x/image v0.27.0
CVE-2026-33814 unknown golang.org/x/net v0.40.0

Showing 13 of 13

Beta — feedback welcome: [email protected]