← Home

bunker

npm Repository

code coverage in native javascript

4
Versions
MIT/X11
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

substack

Keywords

codecoverage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is ~15 years old with 38k weekly downloads by well-known author substack. The 0.0.0 version reflects old conventions, not malicious intent. ai
license uncommon-license:MIT/X11 AI (license): MIT/X11 is a historical variant of the MIT license; no legal or security concern for this package. ai

Versions (showing 4 of 4)

Version Deps Published
0.1.2 1 / 1
0.1.1 1 / 1
0.1.0 1 / 1
0.0.0 1 / 1

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.