@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 100 of 155)
| Version | Deps | Published |
|---|---|---|
| 2.32.0 | 13 / 3 | |
| 2.31.9 | 13 / 3 | |
| 2.31.8 | 13 / 3 | |
| 2.31.7 | 13 / 3 | |
| 2.31.6 | 13 / 3 | |
| 2.31.5 | 13 / 3 | |
| 2.31.4 | 13 / 3 | |
| 2.31.3 | 14 / 3 | |
| 2.31.2 | 14 / 3 | |
| 2.31.1 | 14 / 3 | |
| 2.31.0 | 14 / 3 | |
| 2.30.2 | 13 / 2 | |
| 2.30.1 | 13 / 2 | |
| 2.30.0 | 13 / 2 | |
| 2.29.0 | 13 / 2 | |
| 2.28.4 | 13 / 2 | |
| 2.28.3 | 13 / 2 | |
| 2.28.2 | 13 / 2 | |
| 2.28.1 | 13 / 2 | |
| 2.28.0 | 13 / 2 | |
| 2.27.0 | 13 / 2 | |
| 2.26.6 | 13 / 2 | |
| 2.26.5 | 13 / 2 | |
| 2.26.4 | 13 / 2 | |
| 2.26.3 | 13 / 2 | |
| 2.26.2 | 13 / 2 | |
| 2.26.1 | 13 / 2 | |
| 2.26.0 | 13 / 2 | |
| 2.25.1 | 13 / 2 | |
| 2.25.0 | 13 / 2 | |
| 2.24.5 | 13 / 2 | |
| 2.24.4 | 13 / 2 | |
| 2.24.3 | 13 / 2 | |
| 2.24.2 | 13 / 2 | |
| 2.24.1 | 13 / 2 | |
| 2.24.0 | 13 / 2 | |
| 2.23.2 | 13 / 2 | |
| 2.23.1 | 13 / 2 | |
| 2.23.0 | 13 / 2 | |
| 2.22.5 | 13 / 2 | |
| 2.22.4 | 13 / 2 | |
| 2.22.3 | 13 / 2 | |
| 2.22.2 | 13 / 2 | |
| 2.22.1 | 13 / 2 | |
| 2.22.0 | 13 / 2 | |
| 2.21.6 | 13 / 2 | |
| 2.21.5 | 13 / 2 | |
| 2.21.4 | 13 / 2 | |
| 2.21.3 | 13 / 2 | |
| 2.21.2 | 13 / 2 | |
| 2.21.1 | 13 / 2 | |
| 2.21.0 | 12 / 2 | |
| 2.20.1 | 12 / 2 | |
| 2.20.0 | 12 / 2 | |
| 2.19.0 | 12 / 2 | |
| 2.18.11 | 12 / 2 | |
| 2.18.10 | 12 / 2 | |
| 2.18.9 | 12 / 2 | |
| 2.18.8 | 12 / 2 | |
| 2.18.7 | 12 / 2 | |
| 2.18.6 | 12 / 2 | |
| 2.18.5 | 12 / 2 | |
| 2.18.4 | 12 / 2 | |
| 2.18.3 | 12 / 2 | |
| 2.18.2 | 13 / 2 | |
| 2.18.1 | 13 / 2 | |
| 2.18.0 | 13 / 2 | |
| 2.17.2 | 13 / 2 | |
| 2.17.1 | 13 / 2 | |
| 2.17.0 | 13 / 2 | |
| 2.16.2 | 14 / 2 | |
| 2.16.1 | 14 / 2 | |
| 2.16.0 | 14 / 2 | |
| 2.15.1 | 14 / 2 | |
| 2.15.0 | 14 / 2 | |
| 2.14.3 | 14 / 2 | |
| 2.14.2 | 14 / 2 | |
| 2.14.1 | 14 / 2 | |
| 2.14.0 | 14 / 2 | |
| 2.13.11 | 14 / 2 | |
| 2.13.10 | 14 / 2 | |
| 2.13.9 | 14 / 2 | |
| 2.13.8 | 14 / 2 | |
| 2.13.7 | 14 / 2 | |
| 2.13.6 | 14 / 2 | |
| 2.13.5 | 14 / 2 | |
| 2.13.4 | 14 / 2 | |
| 2.13.3 | 14 / 2 | |
| 2.13.2 | 14 / 2 | |
| 2.13.1 | 14 / 2 | |
| 2.13.0 | 14 / 2 | |
| 2.12.1 | 14 / 2 | |
| 2.12.0 | 14 / 2 | |
| 2.11.7 | 14 / 2 | |
| 2.11.6 | 14 / 2 | |
| 2.11.5 | 14 / 2 | |
| 2.11.4 | 14 / 1 | |
| 2.11.3 | 14 / 1 | |
| 2.11.2 | 14 / 1 | |
| 2.11.1 | 14 / 1 |
v2.31.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.