← Home

remove

npm Repository Homepage
4
Versions
—
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

dsc

Keywords

utilserverfilesfsrmremovedeleterecursive

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Package is ~14 years old, predating Sigstore provenance on npm. This finding will never be resolvable for historical versions. ai
bogus-package bogus-package AI (bogus-package): Old-era package using coco (compiled language); minimal index.js and sparse README are consistent with the package's age and style, not spam. ai

Versions (showing 4 of 4)

Version Deps Published
0.1.5 1 / 3
0.1.2 1 / 2
0.1.1 1 / 2
0.1.0 1 / 2

v0.1.5

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
INFO No provenance attestation provenance

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

v0.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.