@umijs/server
@umijs/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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Legitimate UmiJS scoped package; coincidental Levenshtein match on unscoped name, not a typosquat of semver. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 4.6.63 | 5 / 0 | |
| 4.6.62 | 5 / 0 | |
| 4.6.61 | 5 / 0 | |
| 4.6.59 | 5 / 0 | |
| 4.6.58 | 5 / 0 | |
| 4.6.57 | 5 / 0 | |
| 4.6.56 | 5 / 0 | |
| 3.5.42 | 3 / 0 | |
| 4.5.1-canary.20250928.1 | 5 / 0 | |
| 4.4.13-canary.20250917.1 | 5 / 0 | |
| 4.4.13-canary.20250915.3 | 5 / 0 | |
| 4.4.13-canary.20250915.2 | 5 / 0 | |
| 4.4.13-canary.20250915.1 | 5 / 0 | |
| 4.4.13-canary.20250912.1 | 5 / 0 | |
| 4.4.13-canary.20250911.3 | 5 / 0 | |
| 4.4.13-canary.20250911.1 | 5 / 0 | |
| 4.4.13-canary.20250910.1 | 5 / 0 | |
| 4.0.0-canary.20260325.1 | 5 / 0 | |
| 4.0.0-canary.20260303.1 | 5 / 0 | |
| 4.0.0-canary.20260106.2 | 5 / 0 | |
| 4.0.0-canary.20260106.1 | 5 / 0 | |
| 4.0.0-canary.20260105.1 | 5 / 0 | |
| 4.0.0-canary.20260105.0 | 5 / 0 | |
| 4.0.0-canary.20251209.1 | 5 / 0 | |
| 4.0.0-canary.20251124.1 | 5 / 0 | |
| 4.0.0-canary.20251120.1 | 5 / 0 | |
| 4.0.0-canary.20251116.1 | 5 / 0 | |
| 4.0.0-canary.20251113.1 | 5 / 0 | |
| 4.0.0-canary.20251110.1 | 5 / 0 | |
| 4.0.0-canary.20251104.1 | 5 / 0 | |
| 4.0.0-canary.20251102.1 | 5 / 0 | |
| 4.0.0-canary.20251027.1 | 5 / 0 | |
| 4.0.0-canary.20250918.1 | 5 / 0 | |
| 4.0.0-canary.20250731.1 | 5 / 0 | |
| 4.0.0-canary.20250413.1 | 5 / 0 |
v4.6.63
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (peachscript) than the most recent previously approved version (zoomdong07) on 2026-06-15, but peachscript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.6.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.42
2 findingsPackage name '@umijs/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.