@mescius/wijmo.chart.hierarchical
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:@mescius/wijmo | AI (dependencies): First-party dependency from same publisher/org; version-pinned to matching release. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.chart | AI (dependencies): First-party dependency from same publisher/org; version-pinned to matching release. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.20261.52 | 2 / 0 | |
| 5.20261.50 | 2 / 0 | |
| 5.20261.48 | 2 / 0 | |
| 5.20252.44 | 2 / 0 | |
| 5.20252.42 | 2 / 0 | |
| 5.20251.40 | 2 / 0 | |
| 5.20251.34 | 2 / 0 | |
| 5.20242.30 | 2 / 0 | |
| 5.20242.21 | 2 / 0 | |
| 5.20241.19 | 2 / 0 |
v5.20261.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20251.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20242.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20242.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20241.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.