Security Deep Dive
picoshare
Security posture and CVE patch evidence from tracked releases.
1 critical dependency CVE affects v1.5.4.
Audit transitive dependencies; consider upgrading or pinning replacements.
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
8d 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 v2Vulnerability posture
vulnerability posture
4.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
7.5
10%
Provenance trust
provenance trust
5.0
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 25.2/100OpenSSF 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
1
High
10
Medium
11
Low
2
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-2024-21538 | high | — | cross-spawn | 7.0.3 | 1.5.2 |
| CVE-2024-4068 | high | — | braces | 3.0.2 | 1.5.2 |
| CVE-2025-22869 | high | — | golang.org/x/crypto | v0.0.0-20220331220935-ae2d96664a29 | 1.5.2 |
| CVE-2026-26996 | high | — | minimatch | 5.0.1 | 1.5.2 |
| CVE-2026-27903 | high | — | minimatch | 5.0.1 | 1.5.2 |
| CVE-2026-27904 | high | — | minimatch | 5.0.1 | 1.5.2 |
| CVE-2026-32141 | high | — | flatted | 3.2.5 | 1.5.2 |
| CVE-2026-33228 | high | — | flatted | 3.2.5 | 1.5.2 |
| CVE-2026-33671 | high | — | picomatch | 2.3.1 | 1.5.2 |
| GHSA-5c6j-r48x-rmvq | high | — | serialize-javascript | 6.0.0 | 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-2024-11831 | medium | — | serialize-javascript | 6.0.0 | 1.5.2 |
| CVE-2024-55565 | medium | — | nanoid | 3.3.3 | 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-2025-64718 | medium | — | js-yaml | 4.1.0 | 1.5.2 |
| CVE-2025-69873 | medium | — | ajv | 6.12.6 | 1.5.2 |
| CVE-2026-33672 | medium | — | picomatch | 2.3.1 | 1.5.2 |
| CVE-2026-33750 | medium | — | brace-expansion | 2.0.1 | 1.5.2 |
| CVE-2026-34043 | medium | — | serialize-javascript | 6.0.0 | 1.5.2 |
| CVE-2025-5889 | low | — | brace-expansion | 2.0.1 | 1.5.2 |
| CVE-2026-24001 | low | — | diff | 5.0.0 | 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 26 of 26