@swimlane/ngx-charts
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known/verified via provenance match, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer list cleanup on long-running popular package. | ai | |
| phantom-deps | phantom-dep:d3-transition | AI (phantom-deps): Used via config/build, not direct import; false positive. | ai | |
| phantom-deps | phantom-dep:gradient-path | AI (phantom-deps): Used via config/build, not direct import; false positive. | ai | |
| dependencies | unvetted-dep:gradient-path | AI (dependencies): Legitimate small dep used for gradient path rendering feature. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 24.0.0 | 15 / 0 | |
| 23.1.0 | 15 / 0 | |
| 23.0.1 | 15 / 0 | |
| 23.0.0 | 15 / 0 |
v24.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 (jogaj_26) than the most recent previously approved version (markcoleman1) on 2026-06-17, but jogaj_26 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.
v23.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.