@fiscozen/checkbox
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal design system package; no provenance across all versions, not a security concern for this org. | ai | |
| dependencies | unvetted-dep:@fiscozen/badge | AI (dependencies): Same-org @fiscozen scoped dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@fiscozen/composables | AI (dependencies): Same-org @fiscozen scoped dependency; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/alert | AI (phantom-deps): Same-org design system dep; likely resolved via workspace/peer, not a direct import pattern. | ai | |
| phantom-deps | phantom-dep:@fiscozen/badge | AI (phantom-deps): Same-org design system dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/composables | AI (phantom-deps): Same-org design system dep; stable false positive for this monorepo package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 4 / 18 | |
| 3.0.3 | 4 / 18 | |
| 3.0.2 | 4 / 18 | |
| 3.0.1 | 4 / 18 | |
| 3.0.0 | 4 / 18 | |
| 2.0.0 | 4 / 18 | |
| 1.1.2 | 4 / 18 | |
| 1.1.0 | 4 / 18 | |
| 1.0.1 | 4 / 18 | |
| 1.0.0 | 5 / 18 | |
| 0.2.0 | 2 / 22 |
v3.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (francivago) than the most recent previously approved version (sergioterrasifiscozen) on 2026-05-07, but francivago 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.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.