@gluestack-ui/accordion
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-native-aria/focus | AI (dependencies): Known React Native ARIA primitive; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@react-native-aria/accordion | AI (dependencies): Known React Native ARIA primitive; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@react-native-aria/interactions | AI (dependencies): Known React Native ARIA primitive; stable dependency for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.0.14 | 4 / 10 | |
| 1.0.13 | 4 / 10 | |
| 1.0.12 | 4 / 10 | |
| 1.0.11 | 4 / 10 | |
| 1.0.10 | 4 / 10 | |
| 1.0.9 | 4 / 10 | |
| 1.0.8 | 4 / 10 | |
| 1.0.7 | 4 / 10 | |
| 1.0.6 | 4 / 10 | |
| 1.0.5 | 4 / 10 |
v1.0.13
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.
v1.0.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 (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.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
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.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.