@parcel/watcher-linux-arm64-glibc
A native C++ Node module for querying and subscribing to filesystem events. Used by Parcel 2.
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): This package IS a prebuilt native binary (.node addon) for Linux ARM64. Bundled binary is the entire purpose of the package, not a backdoor risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary sub-packages legitimately have no deps, minimal README, and no keywords. These signals are structural artifacts, not spam indicators. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.5.6 | 0 / 0 | |
| 2.5.4 | 0 / 0 | |
| 2.5.1 | 0 / 0 | |
| 2.5.0 | 0 / 0 | |
| 2.4.1 | 0 / 0 | |
| 2.4.0 | 0 / 0 | |
| 2.3.0 | 0 / 0 | |
| 2.2.0 | 0 / 0 |
v2.5.6
2 findingsPackage contains compiled binaries that could be backdoors: • watcher.node
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
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.0
2 findingsPackage contains compiled binaries that could be backdoors: • watcher.node
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.