autosuggest-highlight
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
moroshkoanubra266dkovalev
Keywords
autosuggestautocompleteauto suggestauto completehighlight autosuggesthighlight autocompletehighlight auto suggesthighlight auto completeautosuggest highlightautocomplete highlightauto suggest highlightauto complete highlight
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in minified IE11 UMD bundle generated by webpack; not dynamic user-controlled code execution. | ai | |
| phantom-deps | phantom-dep:remove-accents | AI (phantom-deps): remove-accents is a declared runtime dependency used in the build; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.3.4 | 1 / 18 |
v3.3.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.