@gluestack-ui/alert-dialog
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): No code changes accompany the maintainer swap; consistent with monorepo team transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy with unchanged content, not a takeover indicator here. | ai | |
| dependencies | unvetted-dep:@react-native-aria/focus | AI (dependencies): Known react-native-aria accessibility library; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@gluestack-ui/hooks | AI (dependencies): First-party gluestack-ui dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@react-native-aria/interactions | AI (dependencies): Known react-native-aria accessibility library; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@react-native-aria/dialog | AI (dependencies): Known react-native-aria accessibility library; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@gluestack-ui/overlay | AI (dependencies): First-party gluestack-ui dependency; stable pattern across all versions of this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.38 | 6 / 10 | |
| 0.1.37 | 6 / 10 | |
| 0.1.36 | 6 / 10 | |
| 0.1.35 | 6 / 10 | |
| 0.1.34 | 6 / 10 | |
| 0.1.33 | 6 / 10 | |
| 0.1.32 | 6 / 10 | |
| 0.1.31 | 6 / 10 | |
| 0.1.30 | 6 / 10 | |
| 0.1.29 | 6 / 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.