@xwiki/platform-editors-blocknote-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@xwiki/platform-rendering-api | AI (dependencies): Same-org monorepo sibling package, versioned in lockstep. | ai | |
| phantom-deps | phantom-dep:@xwiki/platform-uniast-api | AI (phantom-deps): Same-org scoped dep, likely used via type-only or convention import. | ai | |
| dependencies | unvetted-dep:@xwiki/platform-syntaxes-config | AI (dependencies): Same-org monorepo sibling package, versioned in lockstep. | ai | |
| provenance | publisher-changed | AI (provenance): XWiki org internal publisher rotation; consistent with org-managed monorepo publishing pattern. | ai | |
| phantom-deps | phantom-dep:@mantine/hooks | AI (phantom-deps): Referenced in config/peer context for mantine; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xwiki/platform-uniast-markdown | AI (phantom-deps): Same-org scoped package; may be used indirectly via re-exports. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Framework type package loaded by convention; not directly imported. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 18.6.0 | 27 / 21 | |
| 18.5.0 | 23 / 19 | |
| 18.4.2 | 23 / 19 | |
| 18.4.1 | 23 / 19 | |
| 18.4.0 | 23 / 18 | |
| 18.3.0 | 23 / 18 | |
| 18.2.1 | 23 / 16 | |
| 18.2.0 | 23 / 16 | |
| 18.1.0 | 23 / 14 | |
| 18.0.1 | 23 / 14 | |
| 18.0.0 | 23 / 14 |
v18.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (manuelleduc) than the most recent previously approved version (tmortagnee) on 2026-07-27, but manuelleduc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v18.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vmassol) than the most recent previously approved version (michael.hamann) on 2026-06-29, but vmassol is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v18.4.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tmortagnee) than the most recent previously approved version (vmassol) on 2026-06-30, but tmortagnee is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v18.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (michael.hamann) than the most recent previously approved version (tmortagnee) on 2026-02-23, but michael.hamann is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v18.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
v18.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.