@hex-core/components
AI-native React components for Hex UI — Radix UI + Tailwind CSS with machine-readable schemas.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish-env metadata change only; no malicious behavior, stable for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Expected size growth for a growing Radix component library across version gap. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are bundled dist output (schemas.js/.map, dts rollup), not injected code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): shiki/streamdown are established, legitimate packages for a component library. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.13.0 | 36 / 30 | |
| 1.12.0 | 36 / 29 | |
| 1.11.0 | 36 / 29 | |
| 1.10.0 | 36 / 29 | |
| 1.9.0 | 32 / 28 | |
| 1.8.1 | 32 / 28 | |
| 1.8.0 | 32 / 28 | |
| 1.7.0 | 32 / 16 | |
| 1.6.0 | 32 / 16 | |
| 1.5.0 | 31 / 16 | |
| 1.4.0 | 29 / 15 | |
| 1.3.1 | 37 / 5 | |
| 1.3.0 | 37 / 5 | |
| 1.2.1 | 37 / 5 | |
| 1.2.0 | 37 / 5 | |
| 1.1.1 | 37 / 5 | |
| 1.0.1 | 37 / 5 | |
| 1.0.0 | 37 / 5 | |
| 0.2.0 | 37 / 5 | |
| 0.1.0 | 37 / 5 |
v1.12.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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: oscarcorona.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.