@gluestack-ui/button
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-native-aria/focus | AI (dependencies): Known React Native Aria package; stable dependency of gluestack-ui across versions. | ai | |
| dependencies | unvetted-dep:@react-native-aria/interactions | AI (dependencies): Known React Native Aria package; stable dependency of gluestack-ui across versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.14 | 3 / 8 | |
| 1.0.8 | 3 / 8 | |
| 1.0.7 | 3 / 10 | |
| 1.0.6 | 3 / 10 | |
| 1.0.5 | 3 / 10 |
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.