← Home

@fiscozen/typeahead

npm

Design System Typeahead component

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

panicofralen_fiscozentrebhcbfiscozenfrancivagosergioterrasifiscozen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 10 of 10)

Version Deps Published
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.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.