string-hash
fast string hashing function
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Tiny single-function utility with 4.4M weekly downloads; small payload and simple README are expected, not spam indicators. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Rapid publish between v1.1.2 and v1.1.3 is explained by a trivial follow-up change (adding a test script). Package is 13+ years old with a clean history. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by many years; absence is expected for this legacy utility package. | ai |
v1.1.3
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.