← Home

@umijs/core

npm Repository Homepage

See our website [umijs](https://umijs.org) for more information.

6
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): Established monorepo sub-package; sparse README and no keywords are typical for internal scoped packages. ai
dependencies unvetted-dep:@umijs/utils AI (dependencies): @umijs/utils is a sibling package in the same UmiJS monorepo, always published at the same version. This dependency relationship is stable and expected across all versions. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @umijs/core is a legitimate scoped package in the UmiJS monorepo, not a typosquat of 'cors'. This is a stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
4.6.61 2 / 3
4.6.59 2 / 3
4.6.58 2 / 3
4.6.57 2 / 3
4.6.56 2 / 3
4.6.0 2 / 3

v4.6.61

1 finding
LOW No provenance attestation provenance

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

v4.6.59

1 finding
LOW No provenance attestation provenance

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

v4.6.58

1 finding
LOW No provenance attestation provenance

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

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.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.