@ucanto/server
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:semver | AI (typosquat): Scoped package in the ucanto UCAN RPC monorepo; not a typosquat of semver. | ai | |
| dependencies | unvetted-dep:@ucanto/core | AI (dependencies): Internal sibling dependency from the same ucanto monorepo. | ai | |
| dependencies | unvetted-dep:@ucanto/principal | AI (dependencies): Internal sibling dependency from the same ucanto monorepo. | ai | |
| dependencies | unvetted-dep:@ucanto/validator | AI (dependencies): Internal sibling dependency from the same ucanto monorepo. | ai |
v11.0.3
2 findingsPackage name '@ucanto/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
2 findingsPackage name '@ucanto/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.