@parcel/watcher-win32-arm64
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): watcher.node is the expected prebuilt native C++ addon for this platform-specific @parcel/watcher distribution package; stable pattern across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal README, no keywords, and no deps are all expected for a platform-specific binary-only distribution package in the @parcel/watcher ecosystem. | 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsPackage contains compiled binaries that could be backdoors: • watcher.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.