ink-gradient
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
sindresorhus
Keywords
ink-componentinkcomponentgradientgradientscolorcolorsrainbowstylestylesreactjsxterminaltermconsolecommand-line
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/gradient-string | AI (phantom-deps): @types/gradient-string is intentionally listed as a runtime dep by sindresorhus to expose TypeScript types to ESM consumers; not a real phantom dependency issue. | ai | |
| provenance | no-provenance | AI (provenance): sindresorhus packages consistently lack Sigstore provenance; publisher identity is well-established and trusted across hundreds of packages. | ai |
v4.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.