@inkweave/react
React components for InkWeave - ready to use in React applications
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
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 0 / 4 | |
| 2.0.1 | 0 / 4 | |
| 2.0.0 | 0 / 4 | |
| 1.6.0 | 0 / 4 | |
| 1.5.1 | 0 / 4 | |
| 1.5.0 | 0 / 4 | |
| 1.4.2 | 0 / 4 | |
| 1.4.1 | 0 / 4 | |
| 1.3.2 | 0 / 4 | |
| 1.3.1 | 0 / 4 | |
| 1.2.0 | 0 / 10 | |
| 1.1.6 | 0 / 10 | |
| 1.1.5 | 0 / 10 | |
| 1.1.4 | 0 / 10 | |
| 1.1.3 | 0 / 10 | |
| 1.1.2 | 0 / 10 | |
| 1.1.1 | 0 / 8 | |
| 1.1.0 | 0 / 8 | |
| 1.0.0 | 0 / 8 |
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.