is64bit
Check whether operating system CPU architecture is 64-bit or 32-bit (Supports browsers)
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used exclusively to define PE/ELF binary format magic bytes for header inspection — this is the core functionality of the package, not obfuscation or a malicious payload. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Transfer from xan105 to sindresorhus is legitimate; package.json repo/author/funding all point to sindresorhus, consistent with a documented ownership transfer. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to sindresorhus is legitimate; package metadata fully reflects sindresorhus authorship and repo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by ownership transfer; new version modernizes the package under sindresorhus's stewardship. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): system-architecture is a sindresorhus-authored utility directly relevant to this package's purpose; no supply-chain risk. | ai |
v2.0.0
3 findingsAll previous maintainers (xan105) were replaced by new maintainers (sindresorhus). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2023-10-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.