@carbon/charts-angular
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@carbon/telemetry | AI (phantom-deps): Same-org IBM telemetry dep; declared as runtime dependency, phantom-dep heuristic is a false positive here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.27.8 | 3 / 0 | |
| 1.27.3 | 3 / 0 | |
| 1.27.2 | 3 / 0 | |
| 1.27.0 | 3 / 0 | |
| 1.26.1 | 3 / 0 | |
| 1.26.0 | 3 / 0 | |
| 1.25.1 | 3 / 0 | |
| 1.25.0 | 3 / 0 | |
| 1.24.0 | 3 / 0 | |
| 1.23.17 | 3 / 0 | |
| 1.23.16 | 3 / 0 | |
| 1.23.15 | 3 / 0 | |
| 1.23.14 | 3 / 0 | |
| 1.23.13 | 3 / 0 | |
| 1.23.12 | 3 / 0 | |
| 1.23.11 | 3 / 0 | |
| 1.23.10 | 3 / 0 | |
| 1.23.9 | 3 / 0 | |
| 1.23.8 | 3 / 0 | |
| 1.23.7 | 3 / 0 | |
| 1.17.3 | 3 / 0 | |
| 1.8.1 | 3 / 29 |
v1.27.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.