@fiscozen/style
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
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 0 / 19 | |
| 0.3.0 | 0 / 19 | |
| 0.2.0 | 0 / 19 | |
| 0.1.7 | 0 / 12 | |
| 0.1.6 | 0 / 11 | |
| 0.1.5 | 0 / 11 | |
| 0.1.4 | 0 / 10 | |
| 0.1.3 | 0 / 10 | |
| 0.1.2 | 0 / 10 | |
| 0.1.1 | 0 / 10 |
v0.4.0
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.
v0.1.3
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 (alen_fiscozen) on 2024-11-19, 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.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.