@types/slice-ansi
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
types
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): This is a DefinitelyTyped stub/redirect package. Minimal README, no repo link, no keywords, and tiny payload are all expected and correct for this package type. | ai | |
| phantom-deps | phantom-dep:slice-ansi | AI (phantom-deps): slice-ansi is declared as a dependency in the stub redirect pattern — not imported directly. This is the correct structure for a @types stub package. | ai | |
| provenance | no-provenance | AI (provenance): The 'types' publisher has 11,112 approved packages and 0 rejections; lack of provenance attestation is not a concern for this well-established publisher. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 7.1.0 | 1 / 0 |
v7.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.