← Home

@umijs/ast

npm Repository Homepage

@umijs/ast

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sorryccchenshuai2144kuitospeachscriptxiaohuoniyifankakaxixierenyuanxusd320zoomdong07

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 3 of 3)

Show 27 prereleases
Version Deps Published
4.6.57 1 / 0
4.6.56 1 / 0
4.6.47 1 / 0

v4.6.57

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.56

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.