← Home

@vnodes/fs

npm Homepage

@vnodes/fs

14
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

rbrightline

Keywords

fs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @vnodes/fs is a filesystem utility; string similarity to 'qs' is coincidental and not a plausible typosquat. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Same rationale; @vnodes/fs has no relation to the 'pg' postgres client. ai
phantom-deps phantom-dep:@swc/helpers AI (phantom-deps): @swc/helpers is a known implicit runtime dependency injected by SWC transpilation; not a real phantom dep. ai

Versions (showing 14 of 14)

Version Deps Published
0.1.1 1 / 3
0.1.0 1 / 3
0.0.37 1 / 3
0.0.35 1 / 3
0.0.33 1 / 3
0.0.27 1 / 3
0.0.25 1 / 3
0.0.23 1 / 3
0.0.15 1 / 1
0.0.13 1 / 1
0.0.11 1 / 1
0.0.8 2 / 1
0.0.5 2 / 1
0.0.3 2 / 1

v0.1.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@vnodes/fs' is 1 edit(s) away from popular package 'qs'.

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.

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

1 finding
LOW No provenance attestation provenance

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

v0.0.13

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

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