@ant-design/pro-components
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/pro-components.min.js | AI (source-diff): Webpack UMD build output for official ant-design package; benign minified dist, not a dropper. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-form | AI (dependencies): Official sibling package from the same ant-design/pro-components monorepo. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-list | AI (dependencies): Official sibling package from the same ant-design/pro-components monorepo. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-field | AI (dependencies): Official sibling package from the same ant-design/pro-components monorepo. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-table | AI (dependencies): Official sibling package from the same ant-design/pro-components monorepo. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-card | AI (dependencies): Official sibling package from the same ant-design/pro-components monorepo; not a third-party unvetted dep. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-skeleton | AI (dependencies): Official sibling package from the same ant-design/pro-components monorepo. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-descriptions | AI (dependencies): Official sibling package from the same ant-design/pro-components monorepo. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is declared in dependencies and used as a runtime polyfill by transpiled output; not a real phantom dep. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-layout | AI (dependencies): Official sibling package from the same ant-design/pro-components monorepo. | ai |
Versions (showing 77 of 177)
| Version | Deps | Published |
|---|---|---|
| 2.4.12 | 11 / 0 | |
| 2.4.11 | 11 / 0 | |
| 2.4.10 | 11 / 0 | |
| 2.4.9 | 11 / 0 | |
| 2.4.8 | 11 / 0 | |
| 2.4.7 | 11 / 0 | |
| 2.4.6 | 11 / 0 | |
| 2.4.5 | 11 / 0 | |
| 2.4.4 | 11 / 0 | |
| 2.4.3 | 11 / 0 | |
| 2.4.2 | 11 / 0 | |
| 2.4.1 | 11 / 0 | |
| 2.4.0 | 11 / 0 | |
| 2.3.59 | 11 / 0 | |
| 2.3.58 | 11 / 0 | |
| 2.3.57 | 11 / 0 | |
| 2.3.56 | 11 / 0 | |
| 2.3.55 | 11 / 0 | |
| 2.3.54 | 11 / 0 | |
| 2.3.53 | 11 / 0 | |
| 2.3.52 | 11 / 0 | |
| 2.3.51 | 11 / 0 | |
| 2.3.50 | 11 / 0 | |
| 2.3.49 | 11 / 0 | |
| 2.3.48 | 11 / 0 | |
| 2.3.47 | 11 / 0 | |
| 2.3.46 | 11 / 0 | |
| 2.3.45 | 11 / 0 | |
| 2.3.44 | 11 / 0 | |
| 2.3.43 | 11 / 0 | |
| 2.3.42 | 11 / 0 | |
| 2.3.41 | 11 / 0 | |
| 2.3.40 | 11 / 0 | |
| 2.3.39 | 11 / 0 | |
| 2.3.38 | 11 / 0 | |
| 2.3.37 | 11 / 0 | |
| 2.3.36 | 11 / 0 | |
| 2.3.35 | 11 / 0 | |
| 2.3.34 | 11 / 0 | |
| 2.3.33 | 11 / 0 | |
| 2.3.32 | 11 / 0 | |
| 2.3.31 | 11 / 0 | |
| 2.3.30 | 11 / 0 | |
| 2.3.29 | 11 / 0 | |
| 2.3.28 | 11 / 0 | |
| 2.3.27 | 11 / 0 | |
| 2.3.26 | 11 / 0 | |
| 2.3.25 | 11 / 0 | |
| 2.3.24 | 11 / 0 | |
| 2.3.23 | 11 / 0 | |
| 2.3.22 | 11 / 0 | |
| 2.3.21 | 11 / 0 | |
| 2.3.20 | 11 / 0 | |
| 2.3.19 | 11 / 0 | |
| 2.3.18 | 11 / 0 | |
| 2.3.17 | 11 / 0 | |
| 2.3.16 | 11 / 0 | |
| 2.3.15 | 11 / 0 | |
| 2.3.14 | 11 / 0 | |
| 2.3.13 | 11 / 0 | |
| 2.3.12 | 11 / 0 | |
| 2.3.11 | 11 / 0 | |
| 2.3.10 | 11 / 0 | |
| 2.3.9 | 11 / 0 | |
| 2.3.8 | 11 / 0 | |
| 2.3.7 | 11 / 0 | |
| 2.3.6 | 11 / 0 | |
| 2.3.5 | 11 / 0 | |
| 2.3.4 | 11 / 0 | |
| 2.3.3 | 11 / 0 | |
| 2.3.2 | 11 / 0 | |
| 2.3.1 | 11 / 0 | |
| 2.3.0 | 11 / 0 | |
| 2.2.1 | 11 / 0 | |
| 2.2.0 | 11 / 0 | |
| 2.0.1 | 11 / 0 | |
| 2.0.0 | 11 / 0 |
v2.4.12
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.11
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.59
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.58
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.57
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.56
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.55
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.54
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.53
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.