@gluestack-ui/icon
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): Manual publish by known maintainer, no behavioral change in diff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-wide maintainer rotation across gluestack-ui packages, not isolated compromise signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with addition; consistent with normal team turnover for this monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo release cadence; no malicious diff accompanies the gap. | ai | |
| phantom-deps | phantom-dep:@gluestack-ui/provider | AI (phantom-deps): Same-org dep; cross-platform component may use it conditionally. | ai | |
| phantom-deps | phantom-dep:@react-native-aria/focus | AI (phantom-deps): Platform-specific binary dep; not directly imported in all code paths. | ai | |
| phantom-deps | phantom-dep:@gluestack-ui/utils | AI (phantom-deps): Same-org dep; may be re-exported or used indirectly via platform-specific paths. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.27 | 3 / 10 | |
| 0.1.26 | 3 / 10 | |
| 0.1.25 | 3 / 10 | |
| 0.1.23 | 3 / 10 | |
| 0.1.22 | 3 / 10 |
v0.1.26
2 findingsPackage 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-03-11, 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.25
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: viraj-10.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (viraj-10) than the most recent previously approved version (madhavb230100) on 2024-12-03, but viraj-10 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.