@voyantjs/suppliers-react
React runtime package for Voyant booking requirements. Provides the shared provider, typed fetch client, query keys, constants, and TanStack Query hooks that power booking-requirements-focused frontend experiences.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/components/supplier-dialog.js | AI (source-diff): Bundled JSX output with long lines; code is fully readable React components, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/components/supplier-service-row.js | AI (source-diff): Bundled JSX output with long lines; code is fully readable React components, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/components/suppliers-page.js | AI (source-diff): Bundled JSX output with long lines; code is fully readable React components, not obfuscated. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation compensates; package consistently published via GitHub Actions CI. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently published via CI/CD with Sigstore attestation; stable signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD is a legitimate and documented pattern for this monorepo. | ai |
Versions (showing 42 of 242)
| Version | Deps | Published |
|---|---|---|
| 0.26.1 | 1 / 11 | |
| 0.26.0 | 1 / 11 | |
| 0.25.0 | 1 / 11 | |
| 0.24.3 | 1 / 11 | |
| 0.24.2 | 1 / 11 | |
| 0.24.1 | 1 / 11 | |
| 0.24.0 | 1 / 11 | |
| 0.23.0 | 1 / 11 | |
| 0.22.0 | 1 / 11 | |
| 0.21.1 | 1 / 11 | |
| 0.21.0 | 1 / 11 | |
| 0.20.0 | 1 / 11 | |
| 0.19.0 | 1 / 11 | |
| 0.18.0 | 1 / 11 | |
| 0.17.0 | 1 / 11 | |
| 0.16.0 | 1 / 11 | |
| 0.15.0 | 1 / 11 | |
| 0.14.0 | 1 / 11 | |
| 0.13.0 | 1 / 11 | |
| 0.12.0 | 1 / 11 | |
| 0.11.0 | 1 / 11 | |
| 0.10.0 | 1 / 11 | |
| 0.9.0 | 1 / 11 | |
| 0.8.0 | 1 / 11 | |
| 0.7.0 | 1 / 11 | |
| 0.6.9 | 1 / 11 | |
| 0.6.8 | 1 / 11 | |
| 0.6.7 | 1 / 11 | |
| 0.6.5 | 1 / 11 | |
| 0.6.3 | 1 / 11 | |
| 0.6.2 | 1 / 11 | |
| 0.6.0 | 1 / 11 | |
| 0.5.0 | 1 / 11 | |
| 0.4.5 | 1 / 11 | |
| 0.4.4 | 1 / 11 | |
| 0.4.3 | 1 / 11 | |
| 0.4.2 | 1 / 11 | |
| 0.4.1 | 1 / 11 | |
| 0.4.0 | 1 / 11 | |
| 0.3.1 | 1 / 11 | |
| 0.3.0 | 1 / 11 | |
| 0.1.0 | 1 / 11 |
v0.26.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-04-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.