@gluestack-ui/select
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Monorepo team package; new maintainer consistent with org structure, no malicious behavior found. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Sync release cadence across gluestack-ui monorepo packages, not account takeover indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established gluestack-ui package; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.31 | 4 / 10 | |
| 0.1.30 | 4 / 10 | |
| 0.1.29 | 4 / 10 | |
| 0.1.28 | 4 / 10 | |
| 0.1.27 | 4 / 10 |
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.