@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 51 of 177)
| Version | Deps | Published |
|---|---|---|
| 2.8.10 | 11 / 0 | |
| 2.8.9 | 11 / 0 | |
| 2.8.8 | 11 / 0 | |
| 2.8.7 | 11 / 0 | |
| 2.8.6 | 11 / 0 | |
| 2.8.5 | 11 / 0 | |
| 2.8.4 | 11 / 0 | |
| 2.8.3 | 11 / 0 | |
| 2.8.2 | 11 / 0 | |
| 2.8.1 | 11 / 0 | |
| 2.8.0 | 11 / 0 | |
| 2.7.19 | 11 / 0 | |
| 2.7.18 | 11 / 0 | |
| 2.7.17 | 11 / 0 | |
| 2.7.16 | 11 / 0 | |
| 2.7.15 | 11 / 0 | |
| 2.7.14 | 11 / 0 | |
| 2.7.13 | 11 / 0 | |
| 2.7.12 | 11 / 0 | |
| 2.7.11 | 11 / 0 | |
| 2.7.10 | 11 / 0 | |
| 2.7.9 | 11 / 0 | |
| 2.7.8 | 11 / 0 | |
| 2.7.7 | 11 / 0 | |
| 2.7.6 | 11 / 0 | |
| 2.7.5 | 11 / 0 | |
| 2.7.4 | 11 / 0 | |
| 2.7.3 | 11 / 0 | |
| 2.7.2 | 11 / 0 | |
| 2.7.1 | 11 / 0 | |
| 2.7.0 | 11 / 0 | |
| 2.6.52 | 11 / 0 | |
| 2.6.51 | 11 / 0 | |
| 2.6.50 | 11 / 0 | |
| 2.6.49 | 11 / 0 | |
| 2.6.48 | 11 / 0 | |
| 2.6.47 | 11 / 0 | |
| 2.6.46 | 11 / 0 | |
| 2.6.45 | 11 / 0 | |
| 2.6.44 | 11 / 0 | |
| 2.6.43 | 11 / 0 | |
| 2.6.42 | 11 / 0 | |
| 2.6.41 | 11 / 0 | |
| 2.6.40 | 11 / 0 | |
| 2.6.39 | 11 / 0 | |
| 2.6.38 | 11 / 0 | |
| 2.6.37 | 11 / 0 | |
| 2.6.36 | 11 / 0 | |
| 2.6.35 | 11 / 0 | |
| 2.6.34 | 11 / 0 | |
| 2.6.33 | 11 / 0 |
v2.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.6.52
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.6.51
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.6.50
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.6.49
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.6.48
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.6.47
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.6.46
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.6.45
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.6.44
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.6.43
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.6.42
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.6.41
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.6.40
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.6.39
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.6.38
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.6.37
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.6.36
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.6.35
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.6.34
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.6.33
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.