Tools / microsandbox / Security

Security Deep Dive

microsandbox

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 high-severity dependency CVE affects v0.5.4.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 1d 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: 23d ago

Release cadence: weekly Present

1d median over recent releases Release history

Latest release: 3d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 2d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 3d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 3d ago

Signing assets Not active yet

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

Latest release: 3d ago

6.0/10 Security Score

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

1d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

1.00 / 2.5

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

Risk 2.8/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

9.7

10%

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

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

61% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

976 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 (14)

High 1 Medium 3 Low 3 Unknown 7

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
GHSA-3v94-mw7p-v465	high	—	hickory-proto	0.25.2	v0.4.5
CVE-2023-49092	medium	—	rsa	0.9.10	v0.4.5
GHSA-fp55-jw48-c537	medium	—	astral-tokio-tar	0.6.0	v0.4.5
GHSA-q2qq-hmj6-3wpp	medium	—	hickory-proto	0.25.2	v0.4.5
GHSA-2p6r-x3vv-xqm2	low	—	rpassword	7.4.0	v0.4.5
GHSA-cq8v-f236-94qc	low	—	rand	0.8.5	v0.4.5
GHSA-xx64-wwv2-hcqq	low	—	astral-tokio-tar	0.6.0	v0.4.5
RUSTSEC-2025-0134	unknown	—	rustls-pemfile	2.0.0,< 3.0.0	v0.4.5
RUSTSEC-2025-0141	unknown	—	bincode	2.0.1	v0.4.5
RUSTSEC-2026-0097	unknown	—	rand	0.8.5	v0.4.5
RUSTSEC-2026-0112	unknown	—	astral-tokio-tar	0.6.0	v0.4.5
RUSTSEC-2026-0113	unknown	—	astral-tokio-tar	0.6.0	v0.4.5
RUSTSEC-2026-0118	unknown	—	hickory-proto	0.25.2	v0.4.5
RUSTSEC-2026-0119	unknown	—	hickory-proto	0.25.2	v0.4.5

Showing 14 of 14