@parcel/fs-search
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used solely to run 'which ldd' for musl libc detection to select the correct prebuilt native binary. Hardcoded, safe, and a standard napi-rs pattern. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('which ldd') is a hardcoded command for musl detection in native addon binary selection. No user-controlled input; no arbitrary execution risk. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): These are legitimate napi-rs prebuilt platform binaries for a native Node.js addon in the official Parcel bundler monorepo. Expected and stable for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load the correct platform-specific .node binary based on process.platform/arch — canonical napi-rs pattern, not arbitrary code loading. | ai | |
| dependencies | unvetted-dep:detect-libc | AI (dependencies): detect-libc is a standard utility for native addons to distinguish glibc vs musl Linux; its use here is expected and appropriate. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.9.3 | 0 / 1 | |
| 2.9.2 | 0 / 1 | |
| 2.9.1 | 0 / 1 | |
| 2.9.0 | 0 / 1 | |
| 2.8.3 | 1 / 1 | |
| 2.8.2 | 1 / 1 | |
| 2.8.1 | 1 / 1 | |
| 2.8.0 | 1 / 1 | |
| 2.7.0 | 1 / 1 | |
| 2.6.2 | 1 / 1 | |
| 2.6.1 | 1 / 1 | |
| 2.6.0 | 1 / 1 | |
| 2.5.0 | 1 / 1 | |
| 2.4.1 | 1 / 1 | |
| 2.4.0 | 1 / 1 | |
| 2.3.2 | 1 / 1 | |
| 2.3.1 | 1 / 1 | |
| 2.3.0 | 1 / 1 | |
| 2.2.1 | 1 / 1 | |
| 2.2.0 | 1 / 1 | |
| 2.1.1 | 1 / 1 | |
| 2.1.0 | 1 / 1 | |
| 2.0.1 | 1 / 1 | |
| 2.0.0 | 1 / 1 |
v2.9.3
2 findingsPackage contains compiled binaries that could be backdoors: • fs-search.darwin-arm64.node • fs-search.darwin-x64.node • fs-search.linux-arm-gnueabihf.node • fs-search.linux-arm64-gnu.node • fs-search.linux-arm64-musl.node • fs-search.linux-x64-gnu.node • fs-search.linux-x64-musl.node • fs-search.win32-x64-msvc.node
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
2 findingsPackage contains compiled binaries that could be backdoors: • fs-search.darwin-arm64.node • fs-search.darwin-x64.node • fs-search.linux-arm-gnueabihf.node • fs-search.linux-arm64-gnu.node • fs-search.linux-arm64-musl.node • fs-search.linux-x64-gnu.node • fs-search.linux-x64-musl.node • fs-search.win32-x64-msvc.node
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.