@umijs/server
@umijs/server
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo sub-package; terse README is normal, not spam. | ai | |
| phantom-deps | phantom-dep:portfinder | AI (phantom-deps): Used via config/convention in umi dev server, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only dep, expected unused in runtime import scan. | ai | |
| phantom-deps | phantom-dep:@types/spdy | AI (phantom-deps): Type-only dep. | ai | |
| phantom-deps | phantom-dep:@types/sockjs | AI (phantom-deps): Type-only dep. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only dep. | ai | |
| phantom-deps | phantom-dep:@types/compression | AI (phantom-deps): Type-only dep. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Legitimate UmiJS scoped package; coincidental Levenshtein match on unscoped name, not a typosquat of semver. | ai |
Versions (showing 51 of 273)
| Version | Deps | Published |
|---|---|---|
| 4.6.82 | 5 / 0 | |
| 4.6.81 | 5 / 0 | |
| 4.6.80 | 5 / 0 | |
| 4.6.79 | 5 / 0 | |
| 4.6.78 | 5 / 0 | |
| 4.6.77 | 5 / 0 | |
| 4.6.76 | 5 / 0 | |
| 4.6.69 | 5 / 0 | |
| 4.6.68 | 5 / 0 | |
| 4.6.67 | 5 / 0 | |
| 4.6.66 | 5 / 0 | |
| 4.6.65 | 5 / 0 | |
| 4.6.64 | 5 / 0 | |
| 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 | |
| 4.6.55 | 5 / 0 | |
| 4.6.54 | 5 / 0 | |
| 4.6.53 | 5 / 0 | |
| 4.6.52 | 5 / 0 | |
| 4.6.51 | 5 / 0 | |
| 4.6.50 | 5 / 0 | |
| 4.6.49 | 5 / 0 | |
| 4.6.48 | 5 / 0 | |
| 4.6.47 | 5 / 0 | |
| 4.6.46 | 5 / 0 | |
| 4.6.45 | 5 / 0 | |
| 4.6.44 | 5 / 0 | |
| 4.6.43 | 5 / 0 | |
| 4.6.42 | 5 / 0 | |
| 4.6.41 | 5 / 0 | |
| 4.6.40 | 5 / 0 | |
| 4.6.39 | 5 / 0 | |
| 4.6.38 | 5 / 0 | |
| 4.6.37 | 5 / 0 | |
| 4.6.36 | 5 / 0 | |
| 4.6.35 | 5 / 0 | |
| 4.6.34 | 5 / 0 | |
| 4.6.33 | 5 / 0 | |
| 4.6.32 | 5 / 0 | |
| 4.6.31 | 5 / 0 | |
| 4.6.30 | 5 / 0 | |
| 4.6.29 | 5 / 0 | |
| 4.6.28 | 5 / 0 | |
| 4.6.27 | 5 / 0 | |
| 4.6.26 | 5 / 0 | |
| 4.6.25 | 5 / 0 |
v4.6.82
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.81
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.80
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.79
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.78
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.76
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (zoomdong07) on 2026-07-15, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v4.6.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.