@umijs/ast
@umijs/ast
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is a known pattern for UmiJS monorepo sub-packages; not indicative of spam. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @umijs/ast is a scoped UmiJS monorepo package; Levenshtein match to 'jest' is a mechanical false positive with no typosquat intent. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @umijs/ast is a scoped UmiJS monorepo package; Levenshtein match to 'got' is a mechanical false positive with no typosquat intent. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @umijs/ast is a scoped UmiJS monorepo package; Levenshtein match to 'qs' is a mechanical false positive with no typosquat intent. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @umijs/ast is a scoped UmiJS monorepo package; Levenshtein match to 'ajv' is a mechanical false positive with no typosquat intent. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.6.61 | 1 / 0 | |
| 4.6.59 | 1 / 0 | |
| 4.6.58 | 1 / 0 | |
| 4.6.57 | 1 / 0 | |
| 4.6.56 | 1 / 0 | |
| 4.6.47 | 1 / 0 |
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.
v4.6.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.