@udecode/cn
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:pg | AI (typosquat): @udecode/cn is a scoped package in the udecode/plate monorepo; 'cn' is a className utility abbreviation, not a typosquat of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @udecode/cn is a scoped package in the udecode/plate monorepo; 'cn' is a className utility abbreviation, not a typosquat of 'qs'. | ai | |
| dependencies | unvetted-dep:@udecode/react-utils | AI (dependencies): @udecode/react-utils is a sibling package in the same udecode/plate monorepo, published at the same version; this is expected and benign. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 52.3.4 | 2 / 1 | |
| 52.0.11 | 2 / 0 | |
| 52.0.1 | 1 / 0 | |
| 52.0.0 | 1 / 0 | |
| 51.1.2 | 1 / 0 |
v52.3.4
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.