buffer-equal
return whether two buffers are equal
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): substack commonly published early utility packages at 0.0.0; this package is 14 years old with 4.2M weekly downloads — clearly not a throwaway malicious package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm by many years; absence of provenance is expected and not a risk signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate transfer from substack to ljharb (Jordan Harband), a well-known trusted npm maintainer who maintains many packages under inspect-js org. This is a documented stewardship transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ljharb is a well-known, trusted npm maintainer with a strong track record. Addition reflects legitimate stewardship of substack's packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by maintainer transition to ljharb is a known pattern for substack package stewardship transfers, not an account takeover indicator. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 0 / 8 | |
| 1.0.0 | 0 / 1 | |
| 0.0.2 | 0 / 1 | |
| 0.0.1 | 0 / 1 | |
| 0.0.0 | 0 / 1 |
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-10-12. 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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.