@ant-design/pro-form
@ant-design/pro-form
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:use-media-antd-query | AI (phantom-deps): Compiled es/ output not scanned for imports; likely used. | ai | |
| phantom-deps | phantom-dep:rc-resize-observer | AI (phantom-deps): Compiled es/ output not scanned for imports; likely used. | ai | |
| phantom-deps | phantom-dep:use-json-comparison | AI (phantom-deps): Compiled es/ output not scanned for imports; likely used. | ai | |
| phantom-deps | phantom-dep:omit.js | AI (phantom-deps): Compiled es/ output not scanned for imports; likely used. | ai | |
| phantom-deps | phantom-dep:rc-util | AI (phantom-deps): Compiled es/ output not scanned for imports; likely used. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Compiled es/ output not scanned for imports; likely used. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Compiled es/ output not scanned for imports; likely used. | ai | |
| phantom-deps | phantom-dep:@umijs/use-params | AI (phantom-deps): Compiled es/ output not scanned for imports; likely used. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es referenced in build config files only; same pattern as lodash phantom finding. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash referenced in build config files only; standard pattern for this monorepo package. | ai |
Versions (showing 55 of 155)
| Version | Deps | Published |
|---|---|---|
| 2.11.0 | 14 / 1 | |
| 2.10.1 | 14 / 1 | |
| 2.10.0 | 14 / 1 | |
| 2.9.0 | 14 / 1 | |
| 2.8.0 | 14 / 1 | |
| 2.7.0 | 14 / 1 | |
| 2.6.0 | 14 / 1 | |
| 2.5.8 | 14 / 1 | |
| 2.5.7 | 14 / 1 | |
| 2.5.6 | 14 / 1 | |
| 2.5.5 | 14 / 1 | |
| 2.5.4 | 13 / 1 | |
| 2.5.3 | 13 / 1 | |
| 2.5.2 | 13 / 1 | |
| 2.5.1 | 13 / 1 | |
| 2.5.0 | 13 / 1 | |
| 2.4.7 | 13 / 1 | |
| 2.4.6 | 13 / 1 | |
| 2.4.5 | 13 / 1 | |
| 2.4.4 | 13 / 1 | |
| 2.4.3 | 13 / 1 | |
| 2.4.2 | 13 / 1 | |
| 2.4.1 | 13 / 1 | |
| 2.4.0 | 13 / 1 | |
| 2.3.3 | 13 / 1 | |
| 2.3.2 | 13 / 1 | |
| 2.3.1 | 13 / 0 | |
| 2.3.0 | 13 / 0 | |
| 2.2.17 | 13 / 0 | |
| 2.2.16 | 13 / 0 | |
| 2.2.15 | 13 / 0 | |
| 2.2.14 | 13 / 0 | |
| 2.2.13 | 13 / 0 | |
| 2.2.12 | 13 / 0 | |
| 2.2.11 | 13 / 0 | |
| 2.2.10 | 13 / 0 | |
| 2.2.9 | 13 / 0 | |
| 2.2.8 | 13 / 0 | |
| 2.2.7 | 13 / 0 | |
| 2.2.6 | 13 / 0 | |
| 2.2.5 | 13 / 0 | |
| 2.2.4 | 13 / 0 | |
| 2.2.3 | 13 / 0 | |
| 2.2.2 | 13 / 0 | |
| 2.2.1 | 13 / 0 | |
| 2.2.0 | 13 / 0 | |
| 2.1.1 | 13 / 0 | |
| 2.1.0 | 13 / 0 | |
| 2.0.6 | 13 / 0 | |
| 2.0.5 | 13 / 0 | |
| 2.0.4 | 13 / 0 | |
| 2.0.3 | 13 / 0 | |
| 2.0.2 | 13 / 0 | |
| 2.0.1 | 13 / 0 | |
| 2.0.0 | 13 / 0 |
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.