@lexical/plain-text
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/LexicalPlainText.prod.js | AI (source-diff): Standard minified production bundle for this Meta/Facebook package. | ai | |
| source-diff | obfuscated-file:dist/LexicalPlainText.prod.mjs | AI (source-diff): Standard minified production ESM bundle for this Meta/Facebook package. | ai | |
| provenance | no-provenance | AI (provenance): @lexical/plain-text is a Facebook/Meta Lexical ecosystem package; lack of Sigstore provenance is a process gap, not a security risk for this well-established package. | ai | |
| dependencies | unvetted-dep:@lexical/utils | AI (dependencies): Sibling package from the same facebook/lexical monorepo, always released at the same version. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@lexical/dragon | AI (dependencies): Sibling package from the same facebook/lexical monorepo, always released at the same version. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@lexical/clipboard | AI (dependencies): Sibling package from the same facebook/lexical monorepo, always released at the same version. Not a third-party risk. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.45.0 | 6 / 0 | |
| 0.44.0 | 5 / 0 | |
| 0.43.0 | 5 / 0 | |
| 0.42.0 | 5 / 0 | |
| 0.39.0 | 5 / 0 | |
| 0.38.2 | 5 / 0 | |
| 0.38.1 | 5 / 0 | |
| 0.38.0 | 5 / 0 | |
| 0.37.0 | 5 / 0 | |
| 0.36.2 | 5 / 0 | |
| 0.36.1 | 5 / 0 | |
| 0.36.0 | 5 / 0 | |
| 0.35.0 | 4 / 0 | |
| 0.34.0 | 4 / 0 | |
| 0.33.1 | 4 / 0 | |
| 0.33.0 | 4 / 0 | |
| 0.32.1 | 4 / 0 | |
| 0.32.0 | 4 / 0 | |
| 0.31.2 | 4 / 0 | |
| 0.31.1 | 4 / 0 | |
| 0.31.0 | 4 / 0 |
v0.45.0
4 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.
[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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
2 findingsThis version was published by a different npm account than previous versions on 2025-10-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.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.31.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.31.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.