@duckcodeailabs/dql-charts
DQL chart library: visx-powered React SVG components for reusable analytics blocks
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@visx/axis | AI (dependencies): @visx/axis is a legitimate, widely-used open-source visualization library; expected dependency for a visx-based chart package. | ai | |
| dependencies | unvetted-dep:@visx/grid | AI (dependencies): @visx/grid is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/text | AI (dependencies): @visx/text is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/curve | AI (dependencies): @visx/curve is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/group | AI (dependencies): @visx/group is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/scale | AI (dependencies): @visx/scale is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/shape | AI (dependencies): @visx/shape is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/legend | AI (dependencies): @visx/legend is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/tooltip | AI (dependencies): @visx/tooltip is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/gradient | AI (dependencies): @visx/gradient is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| dependencies | unvetted-dep:@visx/responsive | AI (dependencies): @visx/responsive is a legitimate @visx visualization primitive; expected for this chart library. | ai | |
| phantom-deps | phantom-dep:@visx/text | AI (phantom-deps): Minor packaging concern; @visx/text may be used transitively or in config. Not a security issue for this chart library. | ai | |
| phantom-deps | phantom-dep:@visx/legend | AI (phantom-deps): Minor packaging concern; @visx/legend may be used transitively or in config. Not a security issue for this chart library. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 11 / 4 | |
| 1.5.3 | 11 / 4 | |
| 1.5.2 | 11 / 4 | |
| 1.5.1 | 11 / 4 | |
| 1.5.0 | 11 / 4 | |
| 1.4.4 | 11 / 4 | |
| 1.4.3 | 11 / 4 | |
| 1.4.1 | 11 / 4 | |
| 1.4.0 | 11 / 4 | |
| 1.3.6 | 11 / 4 | |
| 1.3.5 | 11 / 4 | |
| 1.3.4 | 11 / 4 | |
| 1.3.2 | 11 / 4 | |
| 1.3.1 | 11 / 4 | |
| 1.3.0 | 11 / 4 | |
| 1.2.2 | 11 / 4 | |
| 1.0.4 | 11 / 4 | |
| 1.0.3 | 11 / 4 | |
| 1.0.2 | 11 / 4 | |
| 1.0.1 | 11 / 4 | |
| 0.11.0 | 11 / 4 | |
| 0.10.2 | 11 / 4 | |
| 0.10.1 | 11 / 4 | |
| 0.10.0 | 11 / 4 | |
| 0.9.0 | 11 / 4 | |
| 0.8.16 | 11 / 4 | |
| 0.8.15 | 11 / 4 | |
| 0.8.14 | 11 / 4 | |
| 0.8.13 | 11 / 4 | |
| 0.8.12 | 11 / 4 | |
| 0.8.11 | 11 / 4 | |
| 0.8.10 | 11 / 4 | |
| 0.8.9 | 11 / 4 | |
| 0.8.8 | 11 / 4 | |
| 0.8.7 | 11 / 4 | |
| 0.8.6 | 11 / 4 | |
| 0.8.5 | 11 / 4 | |
| 0.8.2 | 11 / 4 | |
| 0.8.1 | 11 / 4 | |
| 0.8.0 | 11 / 4 | |
| 0.6.0 | 11 / 4 | |
| 0.1.6 | 11 / 4 | |
| 0.1.5 | 11 / 4 | |
| 0.1.4 | 11 / 4 | |
| 0.1.3 | 11 / 4 | |
| 0.1.2 | 11 / 4 | |
| 0.1.1 | 11 / 4 | |
| 0.1.0 | 11 / 4 |
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.