@gluestack-ui/image
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): Team rotation within trusted gluestack-ui org; publisher has strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with normal maintainer handoff, not takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo package with irregular release cadence, no malicious change accompanying it. | ai | |
| phantom-deps | phantom-dep:@react-native-aria/focus | AI (phantom-deps): Platform-specific dep; not directly imported but legitimately declared for React Native environments. | ai | |
| phantom-deps | phantom-dep:@react-native-aria/interactions | AI (phantom-deps): Platform-specific dep; not directly imported but legitimately declared for React Native environments. | ai | |
| phantom-deps | phantom-dep:@gluestack-ui/utils | AI (phantom-deps): Same-org utility package; phantom-dep flag is a stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.17 | 3 / 10 | |
| 0.1.16 | 3 / 10 | |
| 0.1.15 | 3 / 10 | |
| 0.1.14 | 3 / 10 | |
| 0.1.13 | 3 / 10 | |
| 0.1.12 | 3 / 10 | |
| 0.1.11 | 3 / 10 | |
| 0.1.10 | 3 / 10 |
v0.1.16
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.15
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.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
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.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.