@po-ui/ng-components
PO UI - 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:echarts | AI (phantom-deps): echarts is a known optional chart dep in this Angular library; lazy-loaded pattern means no direct import. | ai | |
| phantom-deps | phantom-dep:driver.js | AI (phantom-deps): driver.js is a legitimate tour library; phantom-dep likely reflects Angular DI/lazy usage pattern. | ai | |
| phantom-deps | phantom-dep:@po-ui/style | AI (phantom-deps): Same-org style package; consumed as a CSS/asset dep, not a JS import. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 21.19.0 | 6 / 0 | |
| 21.18.0 | 6 / 0 | |
| 21.17.0 | 5 / 0 | |
| 21.16.0 | 5 / 0 | |
| 21.15.0 | 5 / 0 | |
| 21.14.0 | 5 / 0 | |
| 21.13.1 | 5 / 0 | |
| 21.13.0 | 5 / 0 | |
| 21.12.0 | 5 / 0 | |
| 21.11.0 | 5 / 0 | |
| 21.10.0 | 5 / 0 | |
| 21.9.0 | 5 / 0 | |
| 21.8.0 | 5 / 0 | |
| 19.39.14 | 5 / 0 | |
| 19.39.13 | 5 / 0 | |
| 19.39.12 | 5 / 0 | |
| 19.39.11 | 5 / 0 | |
| 19.39.10 | 5 / 0 | |
| 19.39.9 | 5 / 0 | |
| 19.39.8 | 5 / 0 |
v21.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.39.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.39.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.39.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.39.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.39.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.39.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.39.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.