@meta2d/chart-diagram
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 |
|---|---|---|---|---|
| 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 8 of 8)
| 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 |
v1.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.