@fiscozen/icons
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is a known maintainer with strong track record; no suspicious changes accompany the dormancy gap. | ai | |
| dependencies | unvetted-dep:@awesome.me/kit-8137893ad3 | AI (dependencies): Font Awesome Pro kit dependency; expected for an icon library in the @fiscozen design system. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped org package @fiscozen/icons; Levenshtein match to 'cors' is a false positive with no plausible impersonation intent. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): @fortawesome/vue-fontawesome is a listed runtime dependency; phantom-dep heuristic misfires for config-registered Vue plugins. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 3 / 18 | |
| 1.0.4 | 3 / 18 | |
| 1.0.2 | 3 / 18 | |
| 1.0.1 | 3 / 18 | |
| 1.0.0 | 3 / 18 | |
| 0.1.37 | 3 / 18 | |
| 0.1.36 | 3 / 3 |
v1.0.5
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 (sergioterrasifiscozen) than the most recent previously approved version (francivago) on 2026-06-04, but sergioterrasifiscozen 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.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.