@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 24 of 124)
| Version | Deps | Published |
|---|---|---|
| 0.3.3 | 3 / 0 | |
| 0.3.2 | 3 / 0 | |
| 0.3.1 | 3 / 0 | |
| 0.3.0 | 3 / 0 | |
| 0.2.9 | 2 / 0 | |
| 0.2.8 | 2 / 0 | |
| 0.2.7 | 2 / 0 | |
| 0.2.6 | 2 / 0 | |
| 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 | |
| 0.1.16 | 2 / 0 | |
| 0.1.15 | 2 / 0 | |
| 0.1.14 | 1 / 0 | |
| 0.1.13 | 1 / 0 | |
| 0.1.12 | 0 / 0 |
v0.3.3
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 (fantactuka) than the most recent previously approved version (zurfyx) on 2022-06-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.3.2
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 (trueadm) 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 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 (fantactuka) than the most recent previously approved version (trueadm) 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 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 (trueadm) than the most recent previously approved version (acywatson) 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 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 (thegreatercurve) than the most recent previously approved version (acywatson) on 2022-05-11, but thegreatercurve 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.8
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 (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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
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 (fantactuka) on 2022-04-28, 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.2.4
2 findingsThis version was published by a different npm account (fantactuka) than the most recent previously approved version (zurfyx) on 2022-04-21. It has since remained available on npm for 1551 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
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 (acywatson) than the most recent previously approved version (zurfyx) on 2022-04-19, 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.2
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 2022-04-18, 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.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
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 (trueadm) than the most recent previously approved version (acywatson) on 2022-04-12, 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.1.20
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 (acywatson) than the most recent previously approved version (trueadm) on 2022-04-07, 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.1.19
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 (acywatson) than the most recent previously approved version (trueadm) on 2022-04-07, 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.1.18
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 (trueadm) than the most recent previously approved version (zurfyx) on 2022-04-07, 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.1.17
2 findingsThis version was published by a different npm account (acywatson) than the most recent previously approved version (zurfyx) on 2022-04-06. It has since remained available on npm for 1566 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
2 findingsThis version was published by a different npm account (acywatson) than the most recent previously approved version (zurfyx) on 2022-03-17. It has since remained available on npm for 1586 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: acywatson.
This version was published by a different npm account (acywatson) than the most recent previously approved version (zurfyx) on 2022-03-16. It has since remained available on npm for 1587 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.