@umijs/plugins MIT 39 versions

@umijs/plugins

npm Repository Homepage

@umijs/plugins

39

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.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Established UmiJS monorepo package; no material changes from prior version; publisher has approved track record.	ai	2026/05/15
dependencies	unvetted-dep:dva-immer	AI (dependencies): Known UmiJS ecosystem dependency; stable across versions of this package.	ai	2026/04/30
dependencies	unvetted-dep:dva-core	AI (dependencies): Known UmiJS ecosystem dependency; stable across versions of this package.	ai	2026/04/30
dependencies	unvetted-dep:dva-loading	AI (dependencies): Known UmiJS ecosystem dependency; stable across versions of this package.	ai	2026/04/30
dependencies	unvetted-dep:@umijs/valtio	AI (dependencies): First-party @umijs scoped package; stable for this package.	ai	2026/04/30
dependencies	unvetted-dep:@umijs/bundler-utils	AI (dependencies): First-party @umijs scoped package; stable for this package.	ai	2026/04/30
dependencies	unvetted-dep:antd-dayjs-webpack-plugin	AI (dependencies): Known Ant Design ecosystem plugin; stable for this package.	ai	2026/04/30
dependencies	unvetted-dep:@ant-design/antd-theme-variable	AI (dependencies): Known Ant Design scoped package; stable for this package.	ai	2026/04/30
dependencies	unvetted-dep:@ant-design/moment-webpack-plugin	AI (dependencies): Known Ant Design scoped package; stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@tanstack/react-query	AI (phantom-deps): Plugin package; referenced in generated config/templates, not directly imported.	ai	2026/04/29
phantom-deps	phantom-dep:@tanstack/react-query-devtools	AI (phantom-deps): Plugin package; referenced in generated config/templates, not directly imported.	ai	2026/04/29
phantom-deps	phantom-dep:styled-components	AI (phantom-deps): Plugin package; referenced in generated config/templates, not directly imported.	ai	2026/04/29
phantom-deps	phantom-dep:moment	AI (phantom-deps): Plugin package; referenced in generated config/templates, not directly imported.	ai	2026/04/29
phantom-deps	phantom-dep:tslib	AI (phantom-deps): Known implicit runtime dependency for TypeScript compiled output.	ai	2026/04/29
phantom-deps	phantom-dep:@ant-design/pro-components	AI (phantom-deps): Plugin package; dependency is injected into user projects, not directly imported.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Monorepo package; sparse metadata is consistent across all @umijs/* packages.	ai	2026/04/29

Versions (showing 39 of 39)

Version	Deps	Published
4.6.56	30 / 2	2026-05-25
4.6.55	30 / 2	2026-05-15
4.6.54	30 / 2	2026-05-14
4.6.53	30 / 2	2026-05-11
4.6.52	30 / 2	2026-05-11
4.6.51	30 / 2	2026-05-06
4.6.50	30 / 2	2026-05-06
4.6.49	30 / 2	2026-04-29
4.6.48	30 / 2	2026-04-27
4.6.47	30 / 2	2026-04-22
4.6.46	30 / 2	2026-04-19
4.6.45	30 / 2	2026-04-16
4.6.44	30 / 2	2026-04-15
4.6.43	30 / 2	2026-04-13
4.6.42	30 / 2	2026-04-10
4.6.41	30 / 2	2026-04-10
4.6.40	30 / 2	2026-04-07
4.6.39	30 / 2	2026-04-01
4.6.38	30 / 2	2026-03-31
4.6.37	30 / 2	2026-03-30
4.6.14	30 / 2	2025-12-24
4.6.13	30 / 2	2025-12-23
4.6.12	30 / 2	2025-12-22
4.6.11	30 / 2	2025-12-22
4.6.10	30 / 2	2025-12-22
4.6.9	30 / 2	2025-12-19
4.6.8	30 / 2	2025-12-18
4.6.7	30 / 2	2025-12-11
4.6.6	30 / 2	2025-12-10
4.6.5	30 / 2	2025-12-05
4.6.4	30 / 2	2025-12-03
4.6.3	30 / 2	2025-12-03
4.6.2	30 / 2	2025-12-02
4.6.1	30 / 2	2025-12-02
4.5.3	30 / 2	2025-10-21
4.5.1	30 / 2	2025-09-25
4.5.0	30 / 2	2025-09-18
4.4.12	30 / 2	2025-07-31
4.4.11	30 / 2	2025-05-15

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

1 finding

LOW No provenance attestation provenance

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

v4.6.54

1 finding

LOW No provenance attestation provenance

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

v4.6.53

1 finding

LOW No provenance attestation provenance

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

v4.6.52

1 finding

LOW No provenance attestation provenance

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

v4.6.51

1 finding

LOW No provenance attestation provenance

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

v4.6.50

1 finding

LOW No provenance attestation provenance

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

v4.6.49

1 finding

LOW No provenance attestation provenance

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

v4.6.48

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.

v4.6.47

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.

v4.6.46

1 finding

LOW No provenance attestation provenance

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

v4.6.45

1 finding

LOW No provenance attestation provenance

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

v4.6.44

1 finding

LOW No provenance attestation provenance

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

v4.6.43

1 finding

LOW No provenance attestation provenance

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

v4.6.42

1 finding

LOW No provenance attestation provenance

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

v4.6.41

1 finding

LOW No provenance attestation provenance

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

v4.6.40

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.

v4.6.39

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.

v4.6.38

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.

v4.6.37

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.

v4.6.14

1 finding

LOW No provenance attestation provenance

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

v4.6.13

1 finding

LOW No provenance attestation provenance

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

v4.6.12

1 finding

LOW No provenance attestation provenance

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

v4.6.11

1 finding

LOW No provenance attestation provenance

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

v4.6.10

1 finding

LOW No provenance attestation provenance

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

v4.6.9

1 finding

LOW No provenance attestation provenance

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

v4.6.8

1 finding

LOW No provenance attestation provenance

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

v4.6.7

1 finding

LOW No provenance attestation provenance

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

v4.6.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: peachscript → zoomdong07 (on 2025-12-10, known maintainer) provenance

This version was published by a different npm account (zoomdong07) than the most recent previously approved version (peachscript) on 2025-12-10, but zoomdong07 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.6.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: peachscript → zoomdong07 (on 2025-12-05, known maintainer) provenance

This version was published by a different npm account (zoomdong07) than the most recent previously approved version (peachscript) on 2025-12-05, but zoomdong07 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.6.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: peachscript → zoomdong07 (on 2025-12-03, known maintainer) provenance

This version was published by a different npm account (zoomdong07) than the most recent previously approved version (peachscript) on 2025-12-03, but zoomdong07 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.6.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: peachscript → zoomdong07 (on 2025-12-03, known maintainer) provenance

This version was published by a different npm account (zoomdong07) than the most recent previously approved version (peachscript) on 2025-12-03, but zoomdong07 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.6.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: peachscript → zoomdong07 (on 2025-12-02, known maintainer) provenance

This version was published by a different npm account (zoomdong07) than the most recent previously approved version (peachscript) on 2025-12-02, but zoomdong07 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.6.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: peachscript → zoomdong07 (on 2025-12-02, known maintainer) provenance

This version was published by a different npm account (zoomdong07) than the most recent previously approved version (peachscript) on 2025-12-02, but zoomdong07 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.5.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sorrycc → peachscript (on 2025-10-21, known maintainer) provenance

This version was published by a different npm account (peachscript) than the most recent previously approved version (sorrycc) on 2025-10-21, but peachscript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.5.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sorrycc → peachscript (on 2025-09-25, known maintainer) provenance

This version was published by a different npm account (peachscript) than the most recent previously approved version (sorrycc) on 2025-09-25, but peachscript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sorrycc → peachscript (on 2025-09-18, known maintainer) provenance

This version was published by a different npm account (peachscript) than the most recent previously approved version (sorrycc) on 2025-09-18, but peachscript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.4.12

1 finding

LOW No provenance attestation provenance

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

v4.4.11

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.