almost-equal
Test if two floats are almost 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): Package is 13+ years old with 772k weekly downloads; 0.0.0 was the author's legitimate initial version choice, not an indicator of malicious intent. | ai | |
| provenance | publisher-changed | AI (provenance): dfcreative is a known maintainer of mikolalysenko packages; this 2016 transition is well-established and legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): dfcreative added as maintainer in 2016; well-known pattern of maintaining mikolalysenko's ecosystem packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a single clean publish during a known maintainer transition; no risk signal. | ai |
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2016-03-09. 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.