@visx/legend
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 monorepo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer roster change in a major version bump of a well-established Airbnb project. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): @types/react is intentionally listed as a runtime dep in visx packages for type resolution; not a security concern and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Airbnb visx monorepo package with clear GitHub repo; lack of provenance attestation is not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 3 / 1 | |
| 3.12.0 | 5 / 0 | |
| 3.10.3 | 5 / 0 | |
| 3.5.0 | 5 / 0 | |
| 3.3.0 | 5 / 0 | |
| 3.2.0 | 5 / 0 | |
| 3.0.0 | 5 / 0 |
v3.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.