@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 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 2 / 1 | |
| 0.3.1 | 2 / 1 | |
| 0.3.0 | 2 / 1 | |
| 0.2.9 | 2 / 1 | |
| 0.2.8 | 2 / 1 | |
| 0.2.7 | 2 / 1 | |
| 0.2.6 | 2 / 1 | |
| 0.2.5 | 2 / 0 | |
| 0.2.4 | 2 / 0 | |
| 0.2.3 | 2 / 0 | |
| 0.2.2 | 2 / 0 | |
| 0.2.1 | 2 / 0 | |
| 0.2.0 | 2 / 0 | |
| 0.1.21 | 2 / 0 | |
| 0.1.20 | 2 / 0 | |
| 0.1.19 | 2 / 0 | |
| 0.1.18 | 2 / 0 | |
| 0.1.17 | 2 / 0 |
v0.3.2
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 (fantactuka) on 2022-06-06, 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.3.1
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 (fantactuka) than the most recent previously approved version (thegreatercurve) on 2022-06-03, but fantactuka 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.3.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 (trueadm) than the most recent previously approved version (thegreatercurve) on 2022-06-02, but trueadm 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.2.9
2 findingsThis version was published by a different npm account (thegreatercurve) than the most recent previously approved version (fantactuka) on 2022-05-11. It has since remained available on npm for 1531 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
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 (acywatson) than the most recent previously approved version (fantactuka) on 2022-05-11, but acywatson 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.2.7
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 (fantactuka) than the most recent previously approved version (zurfyx) on 2022-05-10, but fantactuka 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.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.