@lexical/devtools-core
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/LexicalDevtoolsCore.prod.js | AI (source-diff): Standard production minified bundle for facebook/lexical; stable across versions. | ai | |
| source-diff | obfuscated-file:dist/LexicalDevtoolsCore.prod.mjs | AI (source-diff): Standard production minified ESM bundle for facebook/lexical; stable across versions. | ai | |
| dependencies | unvetted-dep:@lexical/mark | AI (dependencies): Sibling package within the @lexical monorepo, always pinned to the same version. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@lexical/table | AI (dependencies): Sibling package within the @lexical monorepo, always pinned to the same version. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@lexical/html | AI (dependencies): Sibling package within the @lexical monorepo, always pinned to the same version. Not an independent risk. | ai | |
| phantom-deps | phantom-dep:@lexical/utils | AI (phantom-deps): Same-org sibling package; indirect usage in a monorepo build is expected and not a security concern. | ai | |
| dependencies | unvetted-dep:@lexical/utils | AI (dependencies): Sibling package within the @lexical monorepo, always pinned to the same version. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@lexical/link | AI (dependencies): Sibling package within the @lexical monorepo, always pinned to the same version. Not an independent risk. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.45.0 | 6 / 0 | |
| 0.44.0 | 6 / 0 | |
| 0.43.0 | 6 / 0 | |
| 0.42.0 | 6 / 0 | |
| 0.41.0 | 6 / 0 | |
| 0.40.0 | 6 / 0 | |
| 0.39.0 | 6 / 0 | |
| 0.38.2 | 6 / 0 | |
| 0.38.1 | 6 / 0 | |
| 0.38.0 | 6 / 0 | |
| 0.37.0 | 6 / 0 | |
| 0.36.2 | 6 / 0 | |
| 0.36.1 | 6 / 0 | |
| 0.36.0 | 6 / 0 | |
| 0.35.0 | 6 / 0 | |
| 0.34.0 | 6 / 0 | |
| 0.33.1 | 6 / 0 | |
| 0.33.0 | 6 / 0 | |
| 0.32.1 | 6 / 0 | |
| 0.32.0 | 6 / 0 | |
| 0.31.2 | 6 / 0 | |
| 0.31.1 | 6 / 0 | |
| 0.31.0 | 6 / 0 |
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.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.