@ant-design/pro-layout
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:@umijs/ssr-darkreader | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:rc-resize-observer | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:use-json-comparison | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:use-media-antd-query | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:swr | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:omit.js | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:rc-util | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:unstated-next | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:path-to-regexp | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:@umijs/use-params | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:@umijs/route-utils | AI (phantom-deps): Bundled es/ output; used dep not scannable via static import. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai | |
| phantom-deps | phantom-dep:warning | AI (phantom-deps): warning is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai |
Versions (showing 100 of 147)
| Version | Deps | Published |
|---|---|---|
| 7.22.7 | 15 / 3 | |
| 7.22.6 | 15 / 3 | |
| 7.22.5 | 15 / 3 | |
| 7.22.4 | 15 / 3 | |
| 7.22.3 | 15 / 3 | |
| 7.22.2 | 15 / 3 | |
| 7.22.1 | 15 / 3 | |
| 7.22.0 | 16 / 3 | |
| 7.21.2 | 16 / 3 | |
| 7.21.1 | 16 / 3 | |
| 7.21.0 | 16 / 3 | |
| 7.20.2 | 14 / 2 | |
| 7.20.1 | 14 / 2 | |
| 7.20.0 | 14 / 2 | |
| 7.19.12 | 14 / 2 | |
| 7.19.11 | 14 / 1 | |
| 7.19.10 | 14 / 1 | |
| 7.19.9 | 14 / 1 | |
| 7.19.8 | 14 / 1 | |
| 7.19.7 | 14 / 1 | |
| 7.19.6 | 14 / 1 | |
| 7.19.5 | 14 / 1 | |
| 7.19.4 | 14 / 1 | |
| 7.19.3 | 14 / 1 | |
| 7.19.2 | 14 / 1 | |
| 7.19.1 | 14 / 1 | |
| 7.19.0 | 14 / 1 | |
| 7.18.0 | 14 / 1 | |
| 7.17.20 | 14 / 1 | |
| 7.17.19 | 14 / 1 | |
| 7.17.18 | 14 / 1 | |
| 7.17.17 | 14 / 1 | |
| 7.17.16 | 14 / 1 | |
| 7.17.15 | 14 / 1 | |
| 7.17.14 | 14 / 1 | |
| 7.17.13 | 14 / 1 | |
| 7.17.12 | 14 / 1 | |
| 7.17.11 | 14 / 1 | |
| 7.17.10 | 14 / 1 | |
| 7.17.9 | 14 / 1 | |
| 7.17.8 | 14 / 1 | |
| 7.17.7 | 14 / 1 | |
| 7.17.6 | 14 / 1 | |
| 7.17.5 | 14 / 1 | |
| 7.17.4 | 14 / 1 | |
| 7.17.3 | 14 / 1 | |
| 7.17.2 | 14 / 1 | |
| 7.17.1 | 14 / 1 | |
| 7.17.0 | 14 / 1 | |
| 7.16.13 | 14 / 1 | |
| 7.16.12 | 14 / 1 | |
| 7.16.11 | 14 / 1 | |
| 7.16.10 | 15 / 1 | |
| 7.16.9 | 15 / 1 | |
| 7.16.8 | 15 / 1 | |
| 7.16.7 | 15 / 1 | |
| 7.16.6 | 15 / 1 | |
| 7.16.5 | 15 / 1 | |
| 7.16.4 | 16 / 1 | |
| 7.16.3 | 16 / 1 | |
| 7.16.2 | 16 / 1 | |
| 7.16.1 | 16 / 1 | |
| 7.16.0 | 16 / 1 | |
| 7.15.3 | 16 / 1 | |
| 7.15.2 | 16 / 1 | |
| 7.15.1 | 16 / 1 | |
| 7.15.0 | 16 / 1 | |
| 7.14.8 | 16 / 1 | |
| 7.14.7 | 16 / 1 | |
| 7.14.6 | 16 / 1 | |
| 7.14.5 | 16 / 1 | |
| 7.14.4 | 16 / 1 | |
| 7.14.3 | 16 / 1 | |
| 7.14.2 | 16 / 1 | |
| 7.14.1 | 16 / 1 | |
| 7.14.0 | 16 / 1 | |
| 7.13.5 | 16 / 1 | |
| 7.13.4 | 16 / 1 | |
| 7.13.3 | 16 / 1 | |
| 7.13.2 | 16 / 1 | |
| 7.13.1 | 16 / 1 | |
| 7.13.0 | 16 / 1 | |
| 7.12.4 | 16 / 0 | |
| 7.12.3 | 16 / 0 | |
| 7.12.2 | 16 / 0 | |
| 7.12.1 | 16 / 0 | |
| 7.12.0 | 16 / 0 | |
| 7.11.0 | 16 / 0 | |
| 7.10.3 | 16 / 0 | |
| 7.10.2 | 16 / 0 | |
| 7.10.1 | 16 / 0 | |
| 7.10.0 | 16 / 0 | |
| 7.9.0 | 16 / 0 | |
| 7.8.3 | 16 / 0 | |
| 7.8.2 | 16 / 0 | |
| 7.8.1 | 16 / 0 | |
| 7.8.0 | 16 / 0 | |
| 7.7.1 | 17 / 0 | |
| 7.7.0 | 17 / 0 | |
| 7.6.1 | 17 / 0 |
v7.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.