ink
React for CLI
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 | no-provenance | AI (provenance): Established package with strong ecosystem trust; provenance is a best-practice recommendation, not a blocker. | ai | |
| source-diff | large-new-source-files | AI (source-diff): ink is an actively developed framework; large source additions reflect feature work (react-devtools integration, etc.) from a trusted maintainer. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): scheduler and terminal-size are legitimate dependencies fitting ink's purpose as a React CLI renderer; no malicious signal. | ai | |
| dependencies | unvetted-dep:terminal-size | AI (dependencies): terminal-size is a sindresorhus package, part of the same trusted ecosystem as ink's publisher; low risk. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): ink v7.0.0 is a legitimate major version release by the original author (vadimdemedes) after a period of inactivity; consistent with a major rewrite for React 19 / Node 22 support. | ai | |
| dependencies | unvetted-dep:ansi-escapes | AI (dependencies): ansi-escapes is a well-known sindresorhus utility; its use in a CLI rendering library is expected and benign. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): ink is a well-established React-for-CLI library with its own identity; the Levenshtein match to pino is a false positive with no plausible impersonation intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): ink is a legitimate, mature open-source project published by a highly trusted author; inflated semver reflects project history, not spam behavior. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 7.0.5 | 25 / 29 | |
| 7.0.4 | 25 / 29 | |
| 7.0.3 | 25 / 29 | |
| 7.0.2 | 25 / 29 | |
| 7.0.1 | 25 / 29 | |
| 7.0.0 | 25 / 29 | |
| 6.8.0 | 25 / 32 | |
| 6.7.0 | 25 / 30 | |
| 6.6.0 | 23 / 29 | |
| 6.5.1 | 23 / 29 | |
| 6.5.0 | 23 / 29 | |
| 6.4.0 | 23 / 29 | |
| 5.0.1 | 24 / 31 |
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.