@visx/xychart
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; legitimate for airbnb/visx. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer cleanup in a mature org-scoped monorepo; not indicative of takeover. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is a declared runtime dep in a visx monorepo package; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@visx/glyph | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic not meaningful here. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only dep; convention-loaded, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): Type-only dep; convention-loaded, stable false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 16 / 3 | |
| 3.12.0 | 21 / 1 | |
| 3.11.0 | 21 / 1 | |
| 3.10.2 | 21 / 1 | |
| 3.10.1 | 21 / 1 | |
| 3.10.0 | 21 / 1 | |
| 3.9.0 | 21 / 1 | |
| 3.8.0 | 21 / 1 | |
| 3.7.0 | 21 / 1 | |
| 3.5.1 | 21 / 1 | |
| 3.5.0 | 21 / 1 | |
| 3.4.1 | 21 / 1 | |
| 3.4.0 | 21 / 1 | |
| 3.3.0 | 21 / 1 | |
| 3.2.1 | 21 / 1 | |
| 3.2.0 | 21 / 1 | |
| 3.1.3 | 21 / 1 | |
| 3.1.2 | 21 / 1 | |
| 3.1.0 | 21 / 1 | |
| 3.0.2 | 21 / 1 | |
| 3.0.1 | 21 / 1 | |
| 3.0.0 | 21 / 1 |
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.