@trail-ui/react-aria-components
A library of styleable components built using React Aria
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@trail-ui/react | AI (dependencies): Sibling monorepo package from the same publisher; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; provenance absence is common and no other risk signals present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Thin wrapper/re-export package in a monorepo; small payload and minimal README are expected for this type of package. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 1.0.106 | 1 / 0 | |
| 1.0.105 | 1 / 0 | |
| 1.0.104 | 1 / 0 | |
| 1.0.103 | 1 / 0 | |
| 1.0.102 | 1 / 0 | |
| 1.0.101 | 1 / 0 | |
| 1.0.100 | 1 / 0 | |
| 1.0.99 | 1 / 0 | |
| 1.0.98 | 1 / 0 | |
| 1.0.97 | 1 / 0 | |
| 1.0.96 | 1 / 0 | |
| 1.0.95 | 1 / 0 | |
| 1.0.94 | 1 / 0 | |
| 1.0.93 | 1 / 0 | |
| 1.0.92 | 1 / 0 | |
| 1.0.84 | 1 / 0 | |
| 1.0.83 | 1 / 0 | |
| 1.0.82 | 1 / 0 | |
| 1.0.81 | 1 / 0 | |
| 1.0.74 | 1 / 0 | |
| 1.0.73 | 1 / 0 | |
| 1.0.72 | 1 / 0 | |
| 1.0.71 | 1 / 0 | |
| 1.0.70 | 1 / 0 | |
| 1.0.69 | 1 / 0 | |
| 1.0.68 | 1 / 0 | |
| 1.0.67 | 1 / 0 | |
| 1.0.66 | 1 / 0 | |
| 1.0.65 | 1 / 0 | |
| 1.0.64 | 1 / 0 | |
| 1.0.63 | 1 / 0 | |
| 1.0.62 | 1 / 0 | |
| 1.0.61 | 1 / 0 | |
| 1.0.60 | 1 / 0 | |
| 1.0.59 | 1 / 0 | |
| 1.0.58 | 1 / 0 | |
| 1.0.57 | 1 / 0 | |
| 1.0.56 | 1 / 0 | |
| 1.0.55 | 1 / 0 | |
| 1.0.54 | 1 / 0 | |
| 1.0.53 | 1 / 0 | |
| 1.0.52 | 1 / 0 | |
| 1.0.51 | 1 / 0 | |
| 1.0.50 | 1 / 0 | |
| 1.0.49 | 1 / 0 | |
| 1.0.48 | 1 / 0 | |
| 1.0.47 | 1 / 0 | |
| 1.0.46 | 1 / 0 | |
| 1.0.45 | 1 / 0 | |
| 1.0.44 | 1 / 0 | |
| 1.0.43 | 1 / 0 |
v1.0.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.