@trapar-waves/react-antd-pro
A React-based project leveraging Ant Design Pro, TanStack tools, and Rsbuild for efficient enterprise application development
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance and consistent CI/CD publisher mitigate account-takeover concern for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs 'husky' only — standard git-hooks setup, no network fetch or arbitrary code. | ai | |
| phantom-deps | phantom-dep:react-scan | AI (phantom-deps): react-scan is a dev/perf tool referenced in config; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ant-design/pro-layout | AI (phantom-deps): pro-layout is a peer/config-level dep of pro-components; phantom-dep is a stable false positive here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 14 / 27 | |
| 1.1.24 | 14 / 26 | |
| 1.1.23 | 14 / 25 | |
| 1.1.22 | 14 / 25 | |
| 1.1.21 | 14 / 25 | |
| 1.1.19 | 14 / 25 | |
| 1.1.18 | 14 / 25 | |
| 1.1.17 | 14 / 25 | |
| 1.0.16 | 14 / 23 | |
| 1.0.15 | 14 / 19 | |
| 1.0.14 | 14 / 19 | |
| 1.0.13 | 14 / 19 | |
| 1.0.12 | 14 / 19 | |
| 1.0.11 | 14 / 19 | |
| 1.0.10 | 14 / 19 | |
| 1.0.9 | 14 / 19 | |
| 1.0.8 | 14 / 19 | |
| 1.0.7 | 14 / 19 |
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.