@murumets-ee/editor
Block editor — Puck integration, Plate rich text, field mapping, and block renderers.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package content is clean with no other risk signals; likely a CI/publish environment change rather than a supply-chain concern. | ai | |
| source-diff | obfuscated-file:dist/block-editor.mjs | AI (source-diff): Standard minified ESM bundle output from tsdown; code is readable and imports known packages. | ai | |
| source-diff | obfuscated-file:dist/plate.mjs | AI (source-diff): Standard minified ESM bundle output from tsdown; code is readable and imports known packages. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Re-exported icon library; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/link | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/list | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/media | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/table | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Re-exported utility; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/indent | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Re-exported utility; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/markdown | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/autoformat | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/code-block | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/basic-nodes | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-toolbar | AI (phantom-deps): Re-exported component; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-tooltip | AI (phantom-deps): Re-exported component; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:@platejs/floating | AI (phantom-deps): Re-exported plugin; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:platejs | AI (phantom-deps): Re-exported editor framework; declared and used in config files. | ai | |
| phantom-deps | phantom-dep:server-only | AI (phantom-deps): Re-exported utility; declared and used in config files. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.25.0 | 5 / 9 | |
| 0.24.1 | 5 / 9 | |
| 0.24.0 | 5 / 9 | |
| 0.23.2 | 5 / 9 | |
| 0.23.1 | 5 / 9 | |
| 0.23.0 | 5 / 9 | |
| 0.22.1 | 5 / 9 | |
| 0.22.0 | 5 / 9 | |
| 0.21.1 | 5 / 9 | |
| 0.21.0 | 5 / 9 | |
| 0.20.0 | 5 / 9 | |
| 0.19.0 | 5 / 9 | |
| 0.18.0 | 5 / 9 | |
| 0.17.1 | 5 / 9 | |
| 0.17.0 | 5 / 9 | |
| 0.16.5 | 5 / 9 | |
| 0.16.4 | 5 / 9 | |
| 0.16.3 | 5 / 9 | |
| 0.16.2 | 5 / 9 | |
| 0.16.1 | 5 / 9 | |
| 0.16.0 | 5 / 9 | |
| 0.15.4 | 5 / 9 | |
| 0.15.3 | 5 / 9 | |
| 0.15.2 | 5 / 9 | |
| 0.15.1 | 5 / 9 | |
| 0.15.0 | 5 / 9 | |
| 0.14.0 | 5 / 9 | |
| 0.13.3 | 5 / 9 | |
| 0.13.2 | 5 / 9 | |
| 0.13.1 | 5 / 9 | |
| 0.13.0 | 5 / 9 | |
| 0.12.0 | 5 / 9 | |
| 0.11.0 | 20 / 9 | |
| 0.10.0 | 20 / 9 | |
| 0.9.0 | 20 / 9 | |
| 0.8.0 | 20 / 9 | |
| 0.7.0 | 20 / 9 | |
| 0.6.1 | 20 / 9 | |
| 0.6.0 | 20 / 9 | |
| 0.5.1 | 20 / 9 | |
| 0.5.0 | 20 / 9 | |
| 0.4.8 | 19 / 9 | |
| 0.4.6 | 19 / 9 | |
| 0.4.5 | 19 / 9 | |
| 0.4.4 | 19 / 9 | |
| 0.4.0 | 19 / 9 | |
| 0.3.0 | 19 / 9 | |
| 0.1.5 | 19 / 9 | |
| 0.1.4 | 19 / 8 | |
| 0.1.3 | 19 / 8 | |
| 0.1.2 | 19 / 8 | |
| 0.1.1 | 19 / 8 | |
| 0.1.0 | 19 / 8 |
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ranx2k.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.