@dolthub/react-components
A collection of React components for common tasks
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): react-icons is the well-known canonical icons library; swap from @react-icons/all-files is a routine consolidation. | ai | |
| dependencies | unvetted-dep:react-loader | AI (dependencies): Legitimate UI dependency; stable use across this package's versions. | ai | |
| dependencies | unvetted-dep:@dolthub/web-utils | AI (dependencies): First-party DoltHub sibling package; consistent with this library's ecosystem. | ai | |
| dependencies | unvetted-dep:@dolthub/react-hooks | AI (dependencies): First-party DoltHub sibling package; consistent with this library's ecosystem. | ai | |
| dependencies | unvetted-dep:@dolthub/react-contexts | AI (dependencies): First-party DoltHub sibling package; consistent with this library's ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): GitHub Actions publisher; provenance not yet configured for this org's packages but no other risk signals. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 7 / 59 | |
| 0.4.2 | 7 / 59 | |
| 0.4.1 | 7 / 59 | |
| 0.4.0 | 7 / 59 | |
| 0.3.4 | 10 / 63 | |
| 0.3.3 | 10 / 63 | |
| 0.3.2 | 10 / 63 | |
| 0.3.1 | 10 / 63 | |
| 0.3.0 | 10 / 63 |
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.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.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.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.