@ttt-productions/upload-ui
18
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
pignuggetz
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.7.4 | 4 / 1 | |
| 0.5.0 | 4 / 1 | |
| 0.3.5 | 4 / 1 | |
| 0.3.4 | 4 / 1 | |
| 0.3.3 | 4 / 1 | |
| 0.3.2 | 4 / 1 | |
| 0.3.1 | 4 / 1 | |
| 0.3.0 | 4 / 1 | |
| 0.2.9 | 4 / 1 | |
| 0.2.8 | 4 / 1 | |
| 0.2.7 | 4 / 1 | |
| 0.2.6 | 4 / 1 | |
| 0.2.5 | 4 / 1 | |
| 0.2.4 | 4 / 1 | |
| 0.2.3 | 4 / 1 | |
| 0.2.2 | 4 / 1 | |
| 0.2.1 | 5 / 1 | |
| 0.2.0 | 5 / 1 |
v0.7.4
2 findings
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
INFO
Publisher changed: pignuggetz → GitHub Actions (on 2026-07-14, now via trusted publisher with provenance)
provenance
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (pignuggetz) on 2026-07-14, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.