@lofcz/platejs-code-drawing
Code drawing plugin for Plate (PlantUml, Graphviz, Flowchart, Mermaid)
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Inflated semver mirrors upstream plate v52.x fork; not spam, just a scoped fork package. | ai | |
| dependencies | unvetted-dep:flowchart.js | AI (dependencies): flowchart.js is a well-known diagramming library; appropriate for a code-drawing plugin. | ai | |
| dependencies | unvetted-dep:plantuml-encoder | AI (dependencies): plantuml-encoder is a standard utility for PlantUML; appropriate for this plugin's stated purpose. | ai | |
| phantom-deps | phantom-dep:react-compiler-runtime | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this plugin package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Monorepo plugin; lodash declared as dep and used transitively/in config, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:@codemirror/lang-javascript | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this plugin package. | ai | |
| phantom-deps | phantom-dep:@codemirror/theme-one-dark | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this plugin package. | ai | |
| phantom-deps | phantom-dep:@platejs/utils | AI (phantom-deps): Aliased dep (@lofcz/platejs-utils); phantom-dep heuristic misfires on npm aliases. | ai | |
| phantom-deps | phantom-dep:@uiw/react-codemirror | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this plugin package. | ai |
v53.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v52.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.