@ant-design/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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ant-design/graphs | AI (phantom-deps): Same-org peer package re-exported; stable FP. | ai | |
| phantom-deps | phantom-dep:@ant-design/plots | AI (phantom-deps): Same-org peer package re-exported; stable FP. | ai | |
| source-diff | encoded-string-file:dist/charts.min.js | AI (source-diff): Long strings are minified webpack bundle output; stable FP for this build artifact. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.6.7 | 3 / 1 | |
| 2.2.2 | 3 / 0 | |
| 2.2.1 | 2 / 2 | |
| 2.2.0 | 1 / 2 | |
| 2.1.3 | 1 / 2 | |
| 2.1.2 | 1 / 2 | |
| 2.1.1 | 1 / 2 |
v2.2.2
2 findingsThis version was published by a different npm account than previous versions on 2024-10-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.