@ant-design/pro-provider MIT 48 versions

@ant-design/pro-provider

npm Repository Homepage

@ant-design/pro-provider

48

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

afc163zombiejchenshuai2144arvinxxmadccc

Keywords

antdadminant-designant-design-pro

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): @babel/runtime is a framework-scoped package loaded by convention in Ant Design ecosystem packages; phantom detection is a stable false positive here.	ai	2026/04/24
phantom-deps	phantom-dep:rc-util	AI (phantom-deps): rc-util is a standard Ant Design ecosystem dependency referenced in config files; phantom detection is a stable false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:@ant-design/pro-utils	AI (phantom-deps): Same-org dependency from the ant-design/pro-components monorepo; used indirectly/by convention rather than direct import.	ai	2026/04/24

Versions (showing 48 of 148)

Version	Deps	Published
1.5.3	3 / 0	2021-12-10
1.5.2	3 / 0	2021-12-08
1.5.1	3 / 0	2021-12-07
1.5.0	3 / 0	2021-11-30
1.4.20	1 / 0	2021-10-15
1.4.19	1 / 0	2021-09-24
1.4.18	1 / 0	2021-09-16
1.4.17	1 / 0	2021-08-24
1.4.16	1 / 0	2021-07-19
1.4.15	1 / 0	2021-07-01
1.4.14	1 / 0	2021-06-17
1.4.13	1 / 0	2021-06-08
1.4.12	1 / 0	2021-04-29
1.4.11	1 / 0	2021-04-19
1.4.10	1 / 0	2021-04-15
1.4.9	1 / 0	2021-03-29
1.4.8	1 / 0	2021-03-11
1.4.7	1 / 0	2021-03-08
1.4.6	1 / 0	2021-02-28
1.4.5	1 / 0	2021-02-22
1.4.4	1 / 0	2021-01-25
1.4.3	1 / 0	2021-01-21
1.4.2	1 / 0	2021-01-12
1.4.1	1 / 0	2021-01-07
1.4.0	1 / 0	2021-01-05
1.3.1	1 / 0	2021-01-04
1.3.0	1 / 0	2021-01-01
1.2.8	1 / 0	2020-12-31
1.2.7	1 / 0	2020-12-28
1.2.6	1 / 0	2020-12-24
1.2.5	1 / 0	2020-12-21
1.2.4	1 / 0	2020-12-14
1.2.3	1 / 0	2020-12-07
1.2.2	1 / 0	2020-12-02
1.2.1	1 / 0	2020-11-09
1.2.0	1 / 0	2020-11-04
1.1.0	1 / 0	2020-11-02
1.0.1	1 / 0	2020-10-15
1.0.0	1 / 0	2020-10-15
0.2.2	1 / 0	2020-10-12
0.2.1	1 / 0	2020-09-29
0.2.0	1 / 0	2020-09-22
0.1.0	1 / 0	2020-09-07
0.0.6	1 / 0	2020-08-24
0.0.5	1 / 0	2020-08-12
0.0.4	1 / 0	2020-08-12
0.0.3	1 / 0	2020-08-10
0.0.2	1 / 0	2020-07-30

v1.5.3

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.

v1.5.2

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.

v1.5.1

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.

v1.5.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.

v1.4.20

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.

v1.4.19

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.

v1.4.18

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.

v1.4.17

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.

v1.4.16

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.

v1.4.15

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.

v1.4.14

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.

v1.4.13

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.

v1.4.12

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.

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

v1.4.10

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.

v1.4.9

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.

v1.4.8

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.

v1.4.7

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.

v1.4.6

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.

v1.4.5

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.

v1.4.4

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.

v1.4.3

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.

v1.4.2

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.

v1.4.1

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.

v1.4.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.

v1.3.1

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.

v1.3.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.

v1.2.8

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.

v1.2.7

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.

v1.2.6

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.

v1.2.5

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.

v1.2.4

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.

v1.2.3

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.

v1.2.2

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.

v1.2.1

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.

v1.2.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.

v1.1.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.

v1.0.1

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.

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