@enso-ui/typeahead
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@enso-ui/search-mode | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for Vue SFC component imports. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer/config dep in a Vue component library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash referenced in config/build files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/dropdown | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for Vue SFC component imports. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Declared in dependencies; used in config. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Declared in dependencies; used in config. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Declared in dependencies; used in config. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Declared in dependencies; used in config. Stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.1.9 | 4 / 3 | |
| 4.1.8 | 4 / 3 | |
| 4.1.7 | 4 / 3 | |
| 4.1.6 | 4 / 3 | |
| 4.1.5 | 4 / 3 | |
| 4.1.4 | 4 / 3 | |
| 4.1.3 | 4 / 3 | |
| 4.1.2 | 6 / 1 | |
| 4.1.1 | 7 / 0 | |
| 4.1.0 | 7 / 0 | |
| 4.0.0 | 7 / 0 |
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.