@fiscozen/upload
Design System Upload component
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@fiscozen/link | AI (phantom-deps): Same-org dependency; likely re-exported rather than directly imported in source. | ai | |
| phantom-deps | phantom-dep:@fiscozen/button | AI (phantom-deps): Same-org dependency; likely re-exported rather than directly imported in source. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 2 / 18 | |
| 1.0.6 | 2 / 18 | |
| 1.0.5 | 2 / 18 | |
| 1.0.4 | 2 / 18 | |
| 0.1.4 | 2 / 18 |
v1.0.7
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 (trebh) than the most recent previously approved version (sergioterrasifiscozen) on 2026-07-17, but trebh 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.