@akinon/ui-editor
A headless lightweight text editor for Akinon.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yjs | AI (phantom-deps): Peer/plugin dep for collaborative editing; expected for a tiptap-based editor. | ai | |
| phantom-deps | phantom-dep:@tiptap/pm | AI (phantom-deps): Tiptap peer dep re-exported via extensions; stable FP. | ai | |
| phantom-deps | phantom-dep:y-protocols | AI (phantom-deps): Collaboration protocol dep used transitively; stable FP. | ai | |
| phantom-deps | phantom-dep:@tiptap/y-tiptap | AI (phantom-deps): Tiptap collaboration binding; stable FP. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-color | AI (phantom-deps): Tiptap extension registered at runtime; stable FP. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-node-range | AI (phantom-deps): Tiptap extension registered at runtime; stable FP. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-bubble-menu | AI (phantom-deps): Tiptap extension registered at runtime; stable FP. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-drag-handle | AI (phantom-deps): Tiptap extension registered at runtime; stable FP. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-collaboration | AI (phantom-deps): Tiptap extension registered at runtime; stable FP. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.2 | 52 / 6 | |
| 1.0.9 | 52 / 6 | |
| 1.0.8 | 52 / 6 | |
| 1.0.5 | 52 / 6 | |
| 1.0.1 | 51 / 6 |
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.