@interopio/components-react
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:react-flatpickr | AI (phantom-deps): Declared runtime dep; false positive for this component library's import structure. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Component library bundles deps; phantom detection is a false positive for this package's build pattern. | ai | |
| phantom-deps | phantom-dep:react-select | AI (phantom-deps): Component library bundles deps; phantom detection is a false positive for this package's build pattern. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Component library bundles deps; phantom detection is a false positive for this package's build pattern. | ai | |
| phantom-deps | phantom-dep:@accessible/use-id | AI (phantom-deps): Component library bundles deps; phantom detection is a false positive for this package's build pattern. | ai | |
| phantom-deps | phantom-dep:@floating-ui/react | AI (phantom-deps): Component library bundles deps; phantom detection is a false positive for this package's build pattern. | ai | |
| phantom-deps | phantom-dep:framer-motion | AI (phantom-deps): Component library bundles deps; phantom detection is a false positive for this package's build pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 8 / 3 | |
| 0.9.3 | 9 / 3 | |
| 0.9.2 | 9 / 3 | |
| 0.9.1 | 9 / 3 | |
| 0.9.0 | 9 / 2 | |
| 0.8.2 | 9 / 2 |
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.