@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 47 of 147)
| Version | Deps | Published |
|---|---|---|
| 7.6.0 | 17 / 0 | |
| 7.5.2 | 17 / 0 | |
| 7.5.1 | 17 / 0 | |
| 7.5.0 | 17 / 0 | |
| 7.4.0 | 17 / 0 | |
| 7.3.9 | 17 / 0 | |
| 7.3.8 | 17 / 0 | |
| 7.3.7 | 17 / 0 | |
| 7.3.6 | 17 / 0 | |
| 7.3.5 | 17 / 0 | |
| 7.3.4 | 17 / 0 | |
| 7.3.3 | 17 / 0 | |
| 7.3.2 | 17 / 0 | |
| 7.3.1 | 17 / 0 | |
| 7.3.0 | 17 / 0 | |
| 7.2.6 | 18 / 0 | |
| 7.2.5 | 18 / 0 | |
| 7.2.4 | 18 / 0 | |
| 7.2.3 | 18 / 0 | |
| 7.2.2 | 18 / 0 | |
| 7.2.1 | 18 / 0 | |
| 7.2.0 | 18 / 0 | |
| 7.1.16 | 18 / 0 | |
| 7.1.15 | 18 / 0 | |
| 7.1.14 | 18 / 0 | |
| 7.1.13 | 18 / 0 | |
| 7.1.12 | 18 / 0 | |
| 7.1.11 | 18 / 0 | |
| 7.1.10 | 18 / 0 | |
| 7.1.9 | 18 / 0 | |
| 7.1.8 | 18 / 0 | |
| 7.1.7 | 18 / 0 | |
| 7.1.6 | 18 / 0 | |
| 7.1.5 | 18 / 0 | |
| 7.1.4 | 18 / 0 | |
| 7.1.3 | 18 / 0 | |
| 7.1.2 | 18 / 0 | |
| 7.1.1 | 18 / 0 | |
| 7.1.0 | 18 / 0 | |
| 7.0.7 | 18 / 0 | |
| 7.0.6 | 18 / 0 | |
| 7.0.5 | 18 / 0 | |
| 7.0.4 | 18 / 0 | |
| 7.0.3 | 18 / 0 | |
| 7.0.2 | 18 / 0 | |
| 7.0.1 | 18 / 0 | |
| 7.0.0 | 18 / 0 |
v7.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.