Tools / picoshare / Security

Security Deep Dive

picoshare

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v1.5.4.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 3d median Active 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 Unknown

GitHub SBOM API Latest release

—

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 17d ago

Release cadence: weekly Present

3d median over recent releases Release history

Latest release: 8d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 8d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 8d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 8d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 8d ago

4.8/10 Security Score

Dependency Exposure 8 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

1.00 / 1.0

7d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

1.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

-1.50 / 10.0

Risk 25.2/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

7.5

10%

supply chain risk: 25.16 transitive cves: 1c/10h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 7d

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 25.2/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

42% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

154 dependencies scanned View full dependency list →

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

Critical

High

Medium

Low

Unknown

Still affecting latest (8) All (26)

Critical 1 High 1 Medium 4 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2024-45337	critical	—	golang.org/x/crypto	v0.0.0-20220331220935-ae2d96664a29	1.5.2
CVE-2025-22869	high	—	golang.org/x/crypto	v0.0.0-20220331220935-ae2d96664a29	1.5.2
CVE-2023-26115	medium	—	word-wrap	1.2.3	1.5.2
CVE-2023-48795	medium	—	golang.org/x/crypto	v0.0.0-20220331220935-ae2d96664a29	1.5.2
CVE-2025-47914	medium	—	golang.org/x/crypto	v0.0.0-20220331220935-ae2d96664a29	1.5.2
CVE-2025-58181	medium	—	golang.org/x/crypto	v0.0.0-20220331220935-ae2d96664a29	1.5.2
CVE-2022-30636	unknown	—	golang.org/x/crypto	v0.0.0-20220331220935-ae2d96664a29	1.5.2
CVE-2025-47913	unknown	—	golang.org/x/crypto	v0.0.0-20220331220935-ae2d96664a29	1.5.2

Showing 8 of 26