@gluestack-ui/progress
4
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
rajat693sravankumarvelangivaibhk002daminipandeyrayan1810amars29geekgautamgluestackadmingeekashwinividhi499mayankp06madhavb230100viraj-10rohit_singhmeenumakkarsurajahmedc
Keywords
reactnativereact-nativeprogressgluestack-uiuniversalheadlesstypescriptcomponentandroidiosnextjs
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 behavioral change accompanies maintainer swap; likely org reshuffle. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added, no malicious diff present. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy with unchanged content, consistent with monorepo release cadence. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.1.18 | 1 / 10 | |
| 0.1.17 | 1 / 10 | |
| 0.1.16 | 1 / 10 | |
| 0.1.15 | 1 / 10 |
v0.1.17
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.