@uiid/interactive
Interactive components — Accordion, Collapsible, Sortable, Rich Text Editor
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:@uiid/forms | AI (phantom-deps): Same-org monorepo sibling; referenced in config/stories, not direct imports — stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@uiid/tokens | AI (phantom-deps): Same-org monorepo sibling; stable FP. | ai | |
| phantom-deps | phantom-dep:@uiid/overlays | AI (phantom-deps): Same-org monorepo sibling; stable FP. | ai | |
| phantom-deps | phantom-dep:@uiid/indicators | AI (phantom-deps): Same-org monorepo sibling; stable FP. | ai | |
| phantom-deps | phantom-dep:lowlight | AI (phantom-deps): Used via @tiptap/extension-code-block-lowlight config; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/modifiers | AI (phantom-deps): Referenced in config/stories; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/utilities | AI (phantom-deps): Referenced in config/stories; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extensions | AI (phantom-deps): Referenced in config/stories; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/starter-kit | AI (phantom-deps): Referenced in config/stories; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-color | AI (phantom-deps): Referenced in config/stories; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:react-medium-image-zoom | AI (phantom-deps): Referenced in config/stories; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-typography | AI (phantom-deps): Referenced in config/stories; stable FP for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.0.22 | 28 / 21 | |
| 0.0.21 | 28 / 21 | |
| 0.0.20 | 28 / 21 | |
| 0.0.19 | 28 / 21 | |
| 0.0.18 | 28 / 23 | |
| 0.0.17 | 28 / 23 | |
| 0.0.16 | 28 / 23 | |
| 0.0.15 | 28 / 23 | |
| 0.0.14 | 28 / 23 | |
| 0.0.12 | 28 / 23 | |
| 0.0.11 | 28 / 23 | |
| 0.0.10 | 28 / 23 | |
| 0.0.8 | 28 / 23 | |
| 0.0.7 | 28 / 23 |
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.