@fiscozen/container
10
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
panicofralen_fiscozentrebhcbfiscozenfrancivagosergioterrasifiscozen
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 1 / 18 | |
| 0.5.0 | 1 / 18 | |
| 0.4.2 | 1 / 18 | |
| 0.4.1 | 1 / 18 | |
| 0.4.0 | 0 / 18 | |
| 0.3.1 | 0 / 18 | |
| 0.3.0 | 0 / 18 | |
| 0.2.0 | 0 / 18 | |
| 0.1.1 | 0 / 18 | |
| 0.1.0 | 0 / 18 |
v0.5.1
2 findings
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
INFO
Publisher changed: sergioterrasifiscozen → trebh (on 2026-07-17, known maintainer)
provenance
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.