@fiscozen/card
Design System Card 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 — 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@fiscozen/icons | AI (phantom-deps): Same-org dep in a Vue component library; may be re-exported or used indirectly via templates. | ai | |
| phantom-deps | phantom-dep:@fiscozen/button | AI (phantom-deps): Same-org dep in a Vue component library; may be used in SFC templates not caught by static analysis. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped org package @fiscozen/card; Levenshtein match to 'cors' is a false positive with no plausible squatting intent. | ai | |
| phantom-deps | phantom-dep:@fiscozen/style | AI (phantom-deps): Same-org dependency; likely used transitively or via CSS imports not detected by static analysis. | ai | |
| phantom-deps | phantom-dep:@fiscozen/container | AI (phantom-deps): Same-org dependency; likely used transitively or via template/CSS imports. | ai | |
| phantom-deps | phantom-dep:@fiscozen/composables | AI (phantom-deps): Same-org dependency; likely used transitively or via Vue composable patterns not detected statically. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 4 / 18 | |
| 3.0.1 | 4 / 18 | |
| 3.0.0 | 4 / 18 | |
| 2.0.0 | 4 / 18 | |
| 1.1.0 | 4 / 18 | |
| 1.0.2 | 5 / 18 | |
| 1.0.1 | 5 / 18 | |
| 1.0.0 | 5 / 21 | |
| 0.1.6 | 2 / 21 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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 (sergioterrasifiscozen) than the most recent previously approved version (trebh) on 2026-03-03, 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.
v2.0.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 (sergioterrasifiscozen) than the most recent previously approved version (trebh) on 2026-03-02, 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.1.0
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.