@lexical/code
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:LexicalCode.prod.mjs | AI (source-diff): Minified prod build output of official Lexical package, not obfuscation. | ai | |
| phantom-deps | phantom-dep:prismjs | AI (phantom-deps): prismjs is used for code highlighting; likely missed by import scan due to bundling. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same migration; old maintainers removed org-wide, no takeover behavior. | ai | |
| provenance | publisher-changed-stale | AI (provenance): 855-day stale publish rules out takeover; consistent with legitimate account switch. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-wide npm account migration for lexical monorepo, stable across versions. | ai | |
| 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 51 of 118)
| Version | Deps | Published |
|---|---|---|
| 0.48.0 | 4 / 0 | |
| 0.47.0 | 4 / 0 | |
| 0.46.0 | 4 / 0 | |
| 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 | |
| 0.30.0 | 3 / 1 | |
| 0.29.0 | 3 / 1 | |
| 0.28.0 | 3 / 1 | |
| 0.27.2 | 3 / 1 | |
| 0.27.1 | 3 / 1 | |
| 0.27.0 | 3 / 1 | |
| 0.26.0 | 3 / 1 | |
| 0.25.0 | 3 / 1 | |
| 0.24.0 | 3 / 1 | |
| 0.23.1 | 3 / 1 | |
| 0.23.0 | 3 / 1 | |
| 0.22.0 | 3 / 1 | |
| 0.21.0 | 3 / 1 | |
| 0.20.2 | 3 / 1 | |
| 0.20.1 | 3 / 1 | |
| 0.20.0 | 3 / 1 | |
| 0.19.0 | 3 / 1 | |
| 0.18.0 | 3 / 1 | |
| 0.17.1 | 3 / 1 | |
| 0.17.0 | 3 / 1 | |
| 0.16.1 | 3 / 1 | |
| 0.16.0 | 3 / 1 | |
| 0.15.0 | 3 / 1 | |
| 0.14.5 | 3 / 1 | |
| 0.14.4 | 3 / 1 |
v0.48.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zurfyx) than the most recent previously approved version (acywatson) on 2025-02-07, but zurfyx is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
2 findingsNewly 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.14.4
2 findingsNewly 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.