@lexical/clipboard
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org sibling lexical packages, not third-party. | ai | |
| source-diff | obfuscated-file:LexicalClipboard.prod.mjs | AI (source-diff): Minified production build output of official Meta package; no obfuscation signature or malicious behavior. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Historical change from 2022, never unpublished; consistent with legitimate maintainer transfer. | ai | |
| provenance | missing-githead | AI (provenance): Publish-env change on established Facebook monorepo package; no malicious behavior. | ai | |
| phantom-deps | phantom-dep:@lexical/utils | AI (phantom-deps): Same-org @lexical scope dep; benign heuristic FP. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate long-standing maintainer transfer, live 1587d without removal. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing for facebook/lexical monorepo; SLSA attested. | ai | |
| source-diff | obfuscated-file:dist/LexicalClipboard.prod.mjs | AI (source-diff): Standard production minified ESM bundle for this package; stable across versions. | ai | |
| source-diff | obfuscated-file:dist/LexicalClipboard.prod.js | AI (source-diff): Standard production minified bundle for this package; stable across versions. | ai | |
| phantom-deps | phantom-dep:@types/trusted-types | AI (phantom-deps): @types/trusted-types is a TypeScript ambient type package; declaring it as a runtime dep without direct imports is standard practice for type availability. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@lexical/html | AI (dependencies): @lexical/html is a sibling package in the Facebook/Lexical monorepo, always published at the same version. Unvetted status is a pipeline artifact; no real risk. | ai | |
| provenance | no-provenance | AI (provenance): Lexical is a well-established Facebook OSS project; lack of Sigstore provenance is common and not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:@lexical/list | AI (phantom-deps): @lexical/list is a same-org sibling dependency; phantom detection is expected for monorepo packages with conditional/transitive imports. | ai |
Versions (showing 51 of 124)
| Version | Deps | Published |
|---|---|---|
| 0.48.0 | 8 / 0 | |
| 0.47.0 | 8 / 0 | |
| 0.46.0 | 8 / 0 | |
| 0.45.0 | 8 / 0 | |
| 0.44.0 | 7 / 0 | |
| 0.43.0 | 5 / 0 | |
| 0.42.0 | 5 / 0 | |
| 0.41.0 | 5 / 0 | |
| 0.40.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 | 5 / 0 | |
| 0.34.0 | 5 / 0 | |
| 0.33.1 | 5 / 0 | |
| 0.33.0 | 5 / 0 | |
| 0.32.1 | 5 / 0 | |
| 0.32.0 | 5 / 0 | |
| 0.31.2 | 5 / 0 | |
| 0.31.1 | 5 / 0 | |
| 0.31.0 | 5 / 0 | |
| 0.30.0 | 5 / 0 | |
| 0.29.0 | 5 / 0 | |
| 0.28.0 | 5 / 0 | |
| 0.27.2 | 5 / 0 | |
| 0.27.1 | 5 / 0 | |
| 0.27.0 | 5 / 0 | |
| 0.26.0 | 5 / 0 | |
| 0.25.0 | 5 / 0 | |
| 0.24.0 | 5 / 0 | |
| 0.23.1 | 5 / 0 | |
| 0.23.0 | 5 / 0 | |
| 0.22.0 | 5 / 0 | |
| 0.21.0 | 5 / 0 | |
| 0.20.2 | 5 / 0 | |
| 0.20.1 | 5 / 0 | |
| 0.20.0 | 5 / 0 | |
| 0.19.0 | 5 / 0 | |
| 0.18.0 | 5 / 0 | |
| 0.17.1 | 5 / 0 | |
| 0.17.0 | 5 / 0 | |
| 0.16.1 | 5 / 0 | |
| 0.16.0 | 5 / 0 | |
| 0.15.0 | 5 / 0 | |
| 0.14.5 | 5 / 0 | |
| 0.14.4 | 5 / 0 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
2 findings[Accepted risk] Package 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-21, 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.24.0
2 findings[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.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.
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.
[Accepted risk] 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.