@gluestack-ui/input
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): Org-internal maintainer rotation, no other malicious signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Pairs with add; consistent with normal team handoff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo package with batch release cadence, not a takeover indicator alone. | ai | |
| dependencies | unvetted-dep:@react-native-aria/focus | AI (dependencies): Standard React Native ARIA dependency used across gluestack-ui ecosystem; stable pattern. | ai | |
| dependencies | unvetted-dep:@react-native-aria/interactions | AI (dependencies): Standard React Native ARIA dependency used across gluestack-ui ecosystem; stable pattern. | ai | |
| dependencies | unvetted-dep:@gluestack-ui/form-control | AI (dependencies): Sibling gluestack-ui package; expected dependency for this component library. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.38 | 4 / 10 | |
| 0.1.37 | 4 / 10 | |
| 0.1.36 | 4 / 10 | |
| 0.1.35 | 4 / 10 | |
| 0.1.34 | 4 / 10 | |
| 0.1.33 | 4 / 10 | |
| 0.1.32 | 4 / 10 | |
| 0.1.31 | 4 / 10 | |
| 0.1.30 | 4 / 10 |
v0.1.37
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-03, 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.36
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-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.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
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 (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.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.