@platejs/link
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:pino | AI (typosquat): @platejs/link is a scoped package in the official Plate.js editor ecosystem (udecode/plate monorepo); the name similarity to 'pino' is purely coincidental and not an impersonation attempt. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 53.0.3 | 2 / 2 | |
| 53.0.0 | 2 / 2 | |
| 52.3.17 | 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.17
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.