@chainsafe/is-ip
Check if a string is an IP address
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established ChainSafe package with clean history; missing gitHead reflects a publish environment change, not a security concern for this known organization. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 0 / 19 | |
| 2.0.2 | 0 / 19 | |
| 2.0.1 | 0 / 18 | |
| 2.0.0 | 0 / 18 | |
| 1.0.0 | 0 / 18 |
v2.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wemeetagain.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wemeetagain.
v2.0.0
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.