← Home

@parcel/watcher-wasm

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

devongovett

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): watcher.wasm is the package's core WASM artifact; expected for this binding. ai
dependencies unvetted-dep:napi-wasm AI (dependencies): napi-wasm is a legitimate WASM runtime helper, bundled directly in this package as expected for a WASM build of a native module. Not a suspicious dependency. ai
semgrep semgrep:dynamic-require AI (semgrep): The dynamic require is a standard import.meta.url polyfill pattern in bundler-generated CJS output; the string replace trick prevents static rewriting, not malicious obfuscation. ai

Versions (showing 8 of 8)

Version Deps Published
2.6.0 3 / 0
2.5.6 3 / 0
2.5.4 3 / 0
2.5.1 3 / 0
2.5.0 3 / 0
2.4.1 3 / 0
2.4.0 3 / 0
2.3.0 3 / 0

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.1

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • watcher.wasm

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

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • watcher.wasm

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

1 finding
LOW No provenance attestation provenance

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

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

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