@platejs/list
List plugin for Plate
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Plate monorepo package; lack of provenance is consistent across all sibling packages. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @platejs/* package in the udecode/plate monorepo; edit-distance match to 'jest' is purely coincidental. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Monorepo build artifact; clsx is a legitimate runtime dep even if not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Monorepo build artifact; lodash is a legitimate runtime dep even if not directly imported in analyzed files. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 53.0.2 | 4 / 2 | |
| 53.0.0 | 4 / 2 | |
| 52.3.10 | 4 / 2 | |
| 52.0.11 | 3 / 1 | |
| 52.0.1 | 2 / 1 | |
| 52.0.0 | 2 / 1 | |
| 51.1.2 | 2 / 1 |
v53.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v52.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v52.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.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.
v51.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.