@rcsb/rcsb-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 |
|---|---|---|---|---|
| source-diff | net-exec-file:build/charts.js | AI (source-diff): Bundled webpack build of charting UI lib; no malicious network/exec behavior in sample. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs used indirectly via config; standard heuristic false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.28 | 5 / 27 | |
| 0.2.27 | 5 / 31 | |
| 0.2.26 | 7 / 31 | |
| 0.2.25 | 7 / 31 | |
| 0.2.24 | 7 / 30 |
v0.2.28
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.