@umijs/babel-preset-umi
Official babel preset for umi.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer stormslowly; no material change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Team roster change on long-lived monorepo package, no other malicious signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Standard babel plugin ecosystem deps matching preset's stated purpose. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org maintainer rotation, not a takeover pattern here. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual publish to GitHub Actions CI/CD with SLSA attestation; expected for umi monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package; minimal README and no keywords are typical for internal build tools. | ai | |
| dependencies | unvetted-dep:core-js | AI (dependencies): core-js is one of the most widely used polyfill libraries in the JS ecosystem; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-utils | AI (dependencies): Sibling package from the same UmiJS monorepo at matching version; expected dependency pattern for monorepo releases. | ai | |
| dependencies | unvetted-dep:@umijs/utils | AI (dependencies): Sibling package from the same UmiJS monorepo at matching version; expected dependency pattern for monorepo releases. | ai |
Versions (showing 51 of 390)
| 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.75 | 5 / 0 | |
| 4.6.74 | 5 / 0 | |
| 4.6.73 | 5 / 0 | |
| 4.6.72 | 5 / 0 | |
| 4.6.71 | 5 / 0 | |
| 4.6.70 | 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 |
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.75
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.74
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.72
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.70
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.36
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.35
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.34
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.33
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.32
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.31
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zoomdong07.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.