@lexical/code
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@lexical/extension | AI (phantom-deps): Same-org scoped package pinned to the same monorepo release version; declared as a re-export/transitive dep in a monorepo context, not a direct import. Stable false positive. | ai | |
| dependencies | unvetted-dep:prismjs | AI (dependencies): prismjs is a well-known syntax highlighting library; its use in a code-highlighting package is expected and appropriate. Stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @lexical/code is a scoped package in the Facebook Lexical monorepo; Levenshtein comparison to 'cors' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @lexical/code is a scoped package in the Facebook Lexical monorepo; Levenshtein comparison to 'zod' is a false positive with no impersonation intent. | ai | |
| phantom-deps | phantom-dep:lexical | AI (phantom-deps): 'lexical' is the core runtime dependency for all @lexical/* packages; its presence in config files without direct import is expected for this monorepo package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.45.0 | 4 / 0 | |
| 0.44.0 | 4 / 0 | |
| 0.43.0 | 3 / 0 | |
| 0.42.0 | 3 / 0 | |
| 0.41.0 | 3 / 1 | |
| 0.40.0 | 3 / 1 | |
| 0.39.0 | 3 / 1 | |
| 0.38.2 | 3 / 1 | |
| 0.38.1 | 3 / 1 | |
| 0.38.0 | 3 / 1 | |
| 0.37.0 | 3 / 1 | |
| 0.36.2 | 3 / 1 | |
| 0.36.1 | 3 / 1 | |
| 0.36.0 | 3 / 1 | |
| 0.35.0 | 3 / 1 | |
| 0.34.0 | 3 / 1 | |
| 0.33.1 | 3 / 1 | |
| 0.33.0 | 3 / 1 | |
| 0.32.1 | 3 / 1 | |
| 0.32.0 | 3 / 1 | |
| 0.31.2 | 3 / 1 | |
| 0.31.1 | 3 / 1 | |
| 0.31.0 | 3 / 1 |
v0.45.0
1 findingPackage 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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.