is-online
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): silverwind moved to contributors; sindresorhus remains sole publisher, consistent with package history. | ai | |
| provenance | no-provenance | AI (provenance): sindresorhus publishes many packages without provenance; not a risk signal for this publisher. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 1.1.1.1 is Cloudflare's public DNS/connectivity endpoint; using it as a connectivity check is intentional and documented. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects a major version rewrite (got → fetch API); no injected payload. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 12.0.2 | 4 / 2 | |
| 12.0.1 | 4 / 2 | |
| 12.0.0 | 4 / 2 | |
| 10.0.0 | 4 / 3 |
v12.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.