@runtypelabs/ink-components
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:marked-terminal | AI (phantom-deps): Used in examples/config; stable for this package. | ai | |
| phantom-deps | phantom-dep:ink | AI (phantom-deps): Component library re-exports ink; stable pattern for this package type. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): React is peer/re-exported in component library; expected pattern. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Used in examples/config; stable for this package. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Used in examples/config; stable for this package. | ai | |
| phantom-deps | phantom-dep:strip-ansi | AI (phantom-deps): Used in examples/config; stable for this package. | ai | |
| phantom-deps | phantom-dep:ink-spinner | AI (phantom-deps): Component library re-exports ink-spinner; stable pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 7 / 5 | |
| 0.3.0 | 7 / 5 | |
| 0.2.2 | 7 / 5 | |
| 0.2.1 | 7 / 5 | |
| 0.2.0 | 7 / 5 | |
| 0.1.0 | 7 / 5 |
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.