@meta2d/chart-diagram
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/echarts | AI (dependencies): Type-only declaration package; no runtime risk. | ai | |
| dependencies | unvetted-dep:@types/zrender | AI (dependencies): Type-only declaration package; no runtime risk. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Intentional feature: executes user-supplied ECharts init scripts in a diagramming tool context. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): Used to deserialize function strings in chart config objects — expected pattern for this library. | ai | |
| phantom-deps | phantom-dep:@types/echarts | AI (phantom-deps): Type-only dependency; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/zrender | AI (phantom-deps): Type-only dependency; not directly imported at runtime by convention. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.0.23 | 2 / 1 | |
| 1.0.22 | 2 / 1 | |
| 1.0.20 | 2 / 1 | |
| 1.0.19 | 2 / 1 | |
| 1.0.18 | 2 / 1 | |
| 1.0.16 | 2 / 1 | |
| 1.0.15 | 2 / 1 | |
| 1.0.14 | 2 / 1 | |
| 1.0.13 | 1 / 1 | |
| 1.0.12 | 1 / 1 | |
| 1.0.11 | 1 / 1 | |
| 1.0.10 | 1 / 1 | |
| 1.0.9 | 1 / 1 | |
| 1.0.8 | 1 / 1 |
v1.0.13
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 (alsmile) than the most recent previously approved version (anzhusen) on 2024-12-30, but alsmile 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.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.