Tools / figranium / Security

Security Deep Dive

figranium

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 critical dependency CVEs affects v0.13.0.

Audit transitive dependencies; consider upgrading or pinning replacements.

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

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/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 Present

GitHub repository metadata Repository policy

Checked: 13d ago

Release cadence: weekly Present

2d median over recent releases Release history

Latest release: 27d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 18d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 27d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 27d ago

Signing assets Not active yet

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

Latest release: 27d ago

4.2/10 Security Score

Dependency Exposure 42 transitive dependency CVEs found in the latest SBOM. 2 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

11d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.50 / 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 43.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

2.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

5.7

10%

supply chain risk: 42.96 transitive cves: 2c/17h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 11d

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

2 Transitive critical CVEs

0 KEV-transitive CVEs

52% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1914 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 (0) All (42)

Critical 2 High 17 Medium 22 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-41242	critical	—	protobufjs	7.5.4	v0.13.0
GHSA-wpqr-6v78-jr5g	critical	—	@google/gemini-cli	0.29.7	v0.13.0
CVE-2026-1526	high	—	undici	7.22.0	v0.13.0
CVE-2026-1528	high	—	undici	7.22.0	v0.13.0
CVE-2026-2229	high	—	undici	7.22.0	v0.13.0
CVE-2026-26996	high	—	minimatch	3.1.2	v0.13.0
CVE-2026-27606	high	—	rollup	4.54.0	v0.13.0
CVE-2026-27903	high	—	minimatch	10.2.1	v0.13.0
CVE-2026-27904	high	—	minimatch	10.2.1	v0.13.0
CVE-2026-29045	high	—	hono	4.12.3	v0.13.0
CVE-2026-29087	high	—	@hono/node-server	1.19.9	v0.13.0
CVE-2026-29786	high	—	tar	7.5.9	v0.13.0
CVE-2026-30827	high	—	express-rate-limit	8.2.1	v0.13.0
CVE-2026-31802	high	—	tar	7.5.9	v0.13.0
CVE-2026-33671	high	—	picomatch	2.3.1	v0.13.0
CVE-2026-4926	high	—	path-to-regexp	8.3.0	v0.13.0
CVE-2026-6321	high	—	fast-uri	3.1.0	v0.13.0
CVE-2026-6322	high	—	fast-uri	3.1.0	v0.13.0
CVE-2026-6951	high	—	simple-git	3.32.3	v0.13.0
CVE-2026-1525	medium	—	undici	7.22.0	v0.13.0
CVE-2026-1527	medium	—	undici	7.22.0	v0.13.0
CVE-2026-2581	medium	—	undici	7.22.0	v0.13.0
CVE-2026-2739	medium	—	bn.js	4.12.2	v0.13.0
CVE-2026-29085	medium	—	hono	4.12.3	v0.13.0
CVE-2026-29086	medium	—	hono	4.12.3	v0.13.0
CVE-2026-33672	medium	—	picomatch	2.3.1	v0.13.0
CVE-2026-33750	medium	—	brace-expansion	5.0.4	v0.13.0
CVE-2026-39406	medium	—	@hono/node-server	1.19.9	v0.13.0
CVE-2026-39407	medium	—	hono	4.12.3	v0.13.0
CVE-2026-39408	medium	—	hono	4.12.3	v0.13.0
CVE-2026-39409	medium	—	hono	4.12.3	v0.13.0
CVE-2026-39410	medium	—	hono	4.12.3	v0.13.0
CVE-2026-41305	medium	—	postcss	8.5.6	v0.13.0
CVE-2026-41907	medium	—	uuid	13.0.0	v0.13.0
CVE-2026-42338	medium	—	ip-address	10.0.1	v0.13.0
CVE-2026-44455	medium	—	hono	4.12.3	v0.13.0
CVE-2026-44456	medium	—	hono	4.12.3	v0.13.0
CVE-2026-4923	medium	—	path-to-regexp	8.3.0	v0.13.0
GHSA-26pp-8wgv-hjvm	medium	—	hono	4.12.3	v0.13.0
GHSA-458j-xx4x-4375	medium	—	hono	4.12.3	v0.13.0
GHSA-v8w9-8mx6-g223	medium	—	hono	4.12.3	v0.13.0
CVE-2026-3449	low	—	@tootallnate/once	2.0.0	v0.13.0

Showing 42 of 42