@platejs/comment
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:moment | AI (typosquat): Scoped @platejs/* package; Levenshtein match to 'moment' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dependency; phantom-dep heuristic may miss indirect usage in dist bundle. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 53.0.0 | 2 / 2 | |
| 52.3.10 | 2 / 2 | |
| 52.0.11 | 2 / 1 | |
| 52.0.1 | 1 / 1 | |
| 52.0.0 | 1 / 1 | |
| 51.1.2 | 1 / 1 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v52.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v52.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v52.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.