@gluestack-ui/switch
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 | no-provenance | AI (provenance): Gluestack-ui packages consistently publish without provenance; stable false positive for this org. | ai | |
| phantom-deps | phantom-dep:@react-native-aria/focus | AI (phantom-deps): Platform-specific React Native package; not directly imported but legitimately declared as dependency. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.29 | 5 / 10 | |
| 0.1.28 | 5 / 10 | |
| 0.1.27 | 5 / 10 | |
| 0.1.26 | 5 / 10 | |
| 0.1.25 | 5 / 10 | |
| 0.1.24 | 5 / 10 | |
| 0.1.23 | 5 / 10 | |
| 0.1.22 | 5 / 10 |
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
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gluestackadmin) than the most recent previously approved version (madhavb230100) on 2025-02-19, but gluestackadmin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (geekgautam) than the most recent previously approved version (madhavb230100) on 2025-02-18, but geekgautam is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.23
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.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.