← Home

@-xun/project-fs

npm Repository Homepage
8
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

xunnamius

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:rejoinder AI (dependencies): Same publisher ecosystem; no adverse signals. ai
dependencies unvetted-dep:@-xun/fs AI (dependencies): Same publisher (xunnamius) with clean track record; scoped sibling package. ai
dependencies unvetted-dep:@-xun/run AI (dependencies): Same publisher (xunnamius) with clean track record; scoped sibling package. ai
dependencies unvetted-dep:@-xun/project-types AI (dependencies): Same publisher (xunnamius) with clean track record; scoped sibling package. ai
dependencies unvetted-dep:@-xun/memoize AI (dependencies): Same publisher (xunnamius) with clean track record; scoped sibling package. ai
dependencies unvetted-dep:named-app-errors AI (dependencies): Same publisher ecosystem; no adverse signals. ai
provenance no-provenance AI (provenance): Publisher has an established track record; missing provenance is common and not a risk signal here. ai

Versions (showing 8 of 8)

Version Deps Published
2.0.7 9 / 2
2.0.6 9 / 2
2.0.5 9 / 2
2.0.4 9 / 2
2.0.3 9 / 2
2.0.2 9 / 2
2.0.1 9 / 2
2.0.0 9 / 2

v2.0.7

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.

v2.0.6

1 finding
INFO No provenance attestation provenance

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

v2.0.5

1 finding
INFO No provenance attestation provenance

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

v2.0.4

1 finding
INFO No provenance attestation provenance

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

v2.0.3

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.

v2.0.2

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.

v2.0.1

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.

v2.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.