← Home

@visx/axis

npm Repository Homepage
13
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

vx-hshoffhshoffchristopher.card.williams

Keywords

visxreactd3visualizationscharts

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Migrated to GitHub Actions CI/CD publishing with SLSA provenance; legitimate for airbnb/visx. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer roster change consistent with org-level CI/CD migration for this scoped package. ai
typosquat typosquat.levenshtein:axios AI (typosquat): @visx/axis is a legitimate Airbnb visx data visualization package; the Levenshtein match to 'axios' is a false positive based on stripping the scope prefix. Unrelated in purpose. ai
typosquat typosquat.levenshtein:rxjs AI (typosquat): @visx/axis is a legitimate Airbnb visx axis component; the match to 'rxjs' is a false positive. Completely unrelated in purpose and ecosystem. ai
phantom-deps phantom-dep:@types/react AI (phantom-deps): @types/react is intentionally listed as a runtime dependency in visx packages to ensure TypeScript types are available to consumers. This is a stable pattern across the visx monorepo. ai

Versions (showing 13 of 13)

Version Deps Published
4.0.0 6 / 1
3.12.0 8 / 0
3.10.1 8 / 0
3.9.0 8 / 0
3.8.0 8 / 0
3.5.0 8 / 0
3.4.1 8 / 0
3.4.0 8 / 0
3.3.0 8 / 0
3.2.0 8 / 0
3.1.0 8 / 0
3.0.1 8 / 0
3.0.0 8 / 0

v3.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.