@lexical/code-prism
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/LexicalCodePrism.prod.js | AI (source-diff): Standard production minified bundle for @lexical/code-prism; stable across versions. | ai | |
| source-diff | obfuscated-file:dist/LexicalCodePrism.prod.mjs | AI (source-diff): Standard production minified ESM bundle for @lexical/code-prism; stable across versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep @lexical/extension is a same-namespace, same-version sibling package in the Lexical monorepo — consistent with internal refactoring across coordinated releases. | ai | |
| dependencies | unvetted-dep:prismjs | AI (dependencies): prismjs is a well-established syntax highlighting library; its use is expected and appropriate for a code-highlighting package in the Lexical ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Lexical monorepo packages consistently publish without Sigstore provenance; this is a stable characteristic of the package family, not a risk indicator. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.45.0 | 4 / 1 | |
| 0.44.0 | 4 / 1 | |
| 0.43.0 | 3 / 1 | |
| 0.42.0 | 3 / 1 |
v0.45.0
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.