@fiscozen/typeahead
Design System Typeahead 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fiscozen/composables | AI (dependencies): Same-org @fiscozen scoped package; consistent with this design system's dependency pattern. | ai | |
| phantom-deps | phantom-dep:@fiscozen/action | AI (phantom-deps): Same-org design system dep; declared for peer usage, not a phantom risk. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @fiscozen packages; no provenance is the norm for this org. | ai | |
| phantom-deps | phantom-dep:@fiscozen/alert | AI (phantom-deps): Same-org design system dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/progress | AI (phantom-deps): Same-org design system dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fuse.js | AI (phantom-deps): fuse.js is a declared runtime dep used by the typeahead component; likely referenced indirectly via config. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.13 | 7 / 19 | |
| 3.0.12 | 7 / 19 | |
| 3.0.11 | 7 / 19 | |
| 3.0.10 | 7 / 19 | |
| 3.0.8 | 7 / 19 | |
| 3.0.5 | 7 / 19 | |
| 3.0.4 | 7 / 19 | |
| 3.0.3 | 7 / 22 | |
| 3.0.0 | 7 / 22 | |
| 2.0.0 | 7 / 22 | |
| 1.0.4 | 7 / 22 | |
| 1.0.1 | 7 / 22 | |
| 1.0.0 | 8 / 22 |
v3.0.13
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 (sergioterrasifiscozen) than the most recent previously approved version (panicofr) on 2026-06-10, 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.
v3.0.12
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 (sergioterrasifiscozen) than the most recent previously approved version (panicofr) on 2026-06-09, 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.
v3.0.11
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 (panicofr) than the most recent previously approved version (sergioterrasifiscozen) on 2026-06-09, but panicofr 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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.