@lexical/extension
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/LexicalExtension.prod.js | AI (source-diff): Minified production build; standard for Lexical packages. | ai | |
| source-diff | obfuscated-file:dist/LexicalExtension.prod.mjs | AI (source-diff): Minified ESM production build; standard for Lexical packages. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New package in Lexical monorepo; initial set of source files is expected. | ai | |
| source-diff | obfuscated-file:dist/LexicalExtension.dev.js | AI (source-diff): Standard bundled dist output for Lexical monorepo package; inlined preact-signals code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/LexicalExtension.dev.mjs | AI (source-diff): ESM dev bundle with inlined deps; standard Lexical build output. | ai | |
| provenance | no-provenance | AI (provenance): Lexical monorepo packages are published without Sigstore provenance; this is consistent across all versions and not a security concern for this package. | ai | |
| dependencies | unvetted-dep:@lexical/utils | AI (dependencies): @lexical/utils is a sibling package in the official Facebook/Meta Lexical monorepo; always a legitimate dependency for @lexical/extension packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.45.0 | 4 / 0 | |
| 0.44.0 | 3 / 0 | |
| 0.43.0 | 3 / 0 | |
| 0.42.0 | 3 / 0 | |
| 0.41.0 | 3 / 0 | |
| 0.40.0 | 3 / 0 | |
| 0.39.0 | 3 / 0 | |
| 0.38.2 | 3 / 0 | |
| 0.38.1 | 3 / 0 | |
| 0.38.0 | 3 / 0 | |
| 0.37.0 | 3 / 0 | |
| 0.36.2 | 3 / 0 | |
| 0.36.1 | 3 / 0 | |
| 0.36.0 | 3 / 0 |
v0.45.0
6 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zurfyx.
Newly 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.
Newly 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
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: zurfyx.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.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: zurfyx.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.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: zurfyx.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.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.
v0.38.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.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.
v0.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.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.