ng-zorro-antd
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ant-design/icons-angular | AI (dependencies): First-party Ant Design ecosystem dependency; expected and stable for ng-zorro-antd across versions. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 22.0.0 | 5 / 0 | |
| 21.3.3 | 5 / 0 | |
| 21.3.2 | 5 / 0 | |
| 21.3.1 | 5 / 0 | |
| 21.3.0 | 5 / 0 | |
| 21.2.2 | 5 / 0 | |
| 21.2.1 | 5 / 0 | |
| 21.2.0 | 5 / 0 | |
| 21.1.1 | 5 / 0 | |
| 21.1.0 | 5 / 0 | |
| 21.0.2 | 5 / 0 | |
| 21.0.1 | 5 / 0 | |
| 21.0.0 | 5 / 0 | |
| 20.4.4 | 5 / 0 | |
| 20.4.3 | 5 / 0 | |
| 20.4.2 | 5 / 0 | |
| 20.4.1 | 5 / 0 | |
| 20.4.0 | 5 / 0 |
v22.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (laffery) than the most recent previously approved version (zorro-bot) on 2026-01-09, but laffery is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v20.4.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (laffery) than the most recent previously approved version (zorro-bot) on 2025-12-12, but laffery is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v20.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.