@operato/chart
Webcomponents for chart following open-wc recommendations
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): @operato/chart is a scoped chart webcomponent; Levenshtein match to chalk is coincidental and not a typosquat. | ai | |
| phantom-deps | phantom-dep:d3 | AI (phantom-deps): d3 is a declared runtime dependency used in chart rendering; phantom-dep heuristic fires on config-only references. | ai | |
| phantom-deps | phantom-dep:ses | AI (phantom-deps): ses is a declared runtime dependency; phantom-dep heuristic fires on config-only references. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is a declared runtime dependency; phantom-dep heuristic fires on config-only references. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 9.2.25 | 10 / 22 | |
| 9.2.22 | 10 / 22 | |
| 9.2.21 | 10 / 22 | |
| 9.2.20 | 10 / 22 | |
| 9.2.19 | 10 / 22 | |
| 9.2.16 | 10 / 22 | |
| 9.2.15 | 10 / 22 | |
| 9.2.14 | 10 / 22 | |
| 9.2.13 | 10 / 22 | |
| 9.2.6 | 10 / 22 | |
| 9.2.5 | 10 / 22 | |
| 9.2.1 | 10 / 22 | |
| 9.2.0 | 10 / 22 | |
| 8.2.24 | 10 / 22 | |
| 8.2.23 | 10 / 22 | |
| 8.2.22 | 10 / 22 | |
| 8.2.20 | 10 / 22 | |
| 8.2.19 | 10 / 22 | |
| 8.2.18 | 10 / 22 | |
| 8.2.17 | 10 / 22 | |
| 8.2.16 | 10 / 22 | |
| 8.2.15 | 10 / 22 | |
| 8.2.14 | 10 / 22 | |
| 8.2.13 | 10 / 22 |
v9.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.