@ixo/editor
A custom BlockNote editor wrapper for IXO team
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:@tiptap/extension-code | AI (phantom-deps): Listed as runtime dep in package.json; bundled by tsup, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@blocknote/mantine | AI (phantom-deps): Listed as runtime dep in package.json; bundled by tsup, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@tabler/icons-react | AI (phantom-deps): Listed as runtime dep in package.json; bundled by tsup, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@tiptap/core | AI (phantom-deps): Listed as runtime dep in package.json; bundled by tsup, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/core | AI (phantom-deps): Listed as runtime dep in package.json; bundled by tsup, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@blocknote/react | AI (phantom-deps): Listed as runtime dep in package.json; bundled by tsup, not directly imported in source. | ai | |
| provenance | no-provenance | AI (provenance): Established IXO org package; no provenance is a process gap, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:multiformats | AI (phantom-deps): multiformats is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 51 of 122)
| Version | Deps | Published |
|---|---|---|
| 5.20.2 | 13 / 40 | |
| 5.20.1 | 13 / 40 | |
| 5.20.0 | 13 / 40 | |
| 5.19.1 | 13 / 40 | |
| 5.19.0 | 13 / 40 | |
| 5.18.0 | 13 / 40 | |
| 5.15.0 | 13 / 40 | |
| 5.14.0 | 13 / 40 | |
| 5.13.0 | 13 / 40 | |
| 5.12.0 | 13 / 40 | |
| 5.11.0 | 13 / 40 | |
| 5.10.1 | 13 / 40 | |
| 5.10.0 | 13 / 40 | |
| 5.9.1 | 13 / 40 | |
| 5.9.0 | 13 / 40 | |
| 5.8.0 | 11 / 40 | |
| 5.7.0 | 11 / 40 | |
| 5.6.0 | 11 / 40 | |
| 5.5.0 | 11 / 40 | |
| 5.4.0 | 11 / 40 | |
| 5.3.1 | 11 / 40 | |
| 5.3.0 | 11 / 40 | |
| 5.2.0 | 11 / 40 | |
| 5.1.0 | 11 / 40 | |
| 5.0.0 | 11 / 40 | |
| 4.3.1 | 11 / 40 | |
| 4.3.0 | 11 / 40 | |
| 4.2.0 | 11 / 39 | |
| 4.1.0 | 11 / 40 | |
| 4.0.1 | 11 / 40 | |
| 4.0.0 | 11 / 40 | |
| 3.9.0 | 11 / 40 | |
| 3.8.1 | 11 / 40 | |
| 3.8.0 | 11 / 40 | |
| 3.7.0 | 11 / 40 | |
| 3.6.0 | 11 / 40 | |
| 3.5.0 | 11 / 40 | |
| 3.4.3 | 11 / 40 | |
| 3.4.2 | 11 / 40 | |
| 3.4.1 | 11 / 40 | |
| 3.4.0 | 11 / 40 | |
| 3.3.0 | 11 / 40 | |
| 3.2.2 | 11 / 40 | |
| 3.2.1 | 11 / 40 | |
| 3.2.0 | 11 / 40 | |
| 3.1.0 | 11 / 40 | |
| 3.0.0 | 11 / 40 | |
| 2.43.0 | 8 / 34 | |
| 2.42.0 | 8 / 34 | |
| 2.41.0 | 8 / 34 | |
| 2.40.0 | 8 / 34 |
v5.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.