← Home

bfs-path

An emulation of Node's path module. Used in BrowserFS.

6
Versions
MIT
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

jvilk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process is used only in prepublish.js to invoke the TypeScript compiler (tsc) at publish time. This is a benign build script, not consumer-facing install-time code. ai
semgrep semgrep:child-process-spawn AI (semgrep): spawn() in prepublish.js calls tsc for TypeScript compilation before publishing. Stable false positive for this build-tooling pattern. ai
provenance no-provenance AI (provenance): Established 11-year-old package with consistent publisher history; lack of Sigstore provenance is common and not a risk signal here. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.2 0 / 2
1.0.0 1 / 1
0.1.2 0 / 1
0.1.1 0 / 2
0.1.0 0 / 2
0.0.1 0 / 0

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

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

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

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