@amsom-habitat/amsom-autocomplete
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index-CVkHbwPA.js | AI (source-diff): Standard Vite minified bundle; Vue component imports visible at top of file. | ai | |
| source-diff | net-exec-file:dist/index.es-DdIX0nGD-BGEOe1oI.js | AI (source-diff): Function('return this')() is a core-js/polyfill global detection pattern, not malware. | ai | |
| source-diff | net-exec-file:dist/index.es-DdIX0nGD-DwC-nuHT.js | AI (source-diff): Function('return this') is a core-js global detection pattern; no actual network+exec dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/index-wty8ySJY.js | AI (source-diff): Standard Vite-bundled Vue/Font Awesome output; minified but not obfuscated or malicious. | ai | |
| source-diff | encoded-string-file:dist/amsom-autocomplete.umd.cjs | AI (source-diff): Long strings in sample are TypeScript helpers and license text, not encoded payloads. | ai | |
| source-diff | obfuscated-file:dist/index-DBvFYSw9.js | AI (source-diff): Standard Vite-minified bundle; sample shows Vue/FontAwesome imports, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index.es-DdIX0nGD-B1IzItEf.js | AI (source-diff): Function('return this') is core-js global detection idiom; no actual network+exec payload. | ai | |
| phantom-deps | phantom-dep:bootstrap | AI (phantom-deps): Bootstrap is a peer dependency for styling; declared and used via config, not direct import. | ai | |
| phantom-deps | phantom-dep:@amsom-habitat/bootstrap-5 | AI (phantom-deps): Scoped org dependency; likely re-exported or used indirectly in component library. | ai | |
| phantom-deps | phantom-dep:@amsom-habitat/ui | AI (phantom-deps): Scoped org dependency; likely re-exported or used indirectly in component library. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 2.4.21 | 3 / 19 | |
| 2.4.20 | 3 / 19 | |
| 2.4.16 | 4 / 22 | |
| 2.4.15 | 4 / 22 | |
| 2.4.14 | 4 / 22 | |
| 2.4.13 | 4 / 22 | |
| 2.4.11 | 4 / 22 | |
| 2.4.10 | 4 / 22 | |
| 2.4.9 | 4 / 22 | |
| 2.4.8 | 4 / 22 | |
| 2.4.7 | 4 / 22 | |
| 2.4.6 | 4 / 22 | |
| 2.4.5 | 3 / 22 | |
| 2.4.4 | 3 / 22 | |
| 2.4.3 | 4 / 22 | |
| 2.4.2 | 4 / 22 | |
| 2.4.1 | 4 / 22 | |
| 2.4.0 | 4 / 22 | |
| 2.3.0 | 3 / 22 | |
| 2.2.10 | 3 / 22 | |
| 2.2.9 | 3 / 22 | |
| 2.2.8 | 3 / 22 | |
| 2.2.7 | 3 / 22 | |
| 2.2.6 | 3 / 22 | |
| 2.2.5 | 3 / 22 | |
| 2.2.4 | 3 / 22 | |
| 2.2.3 | 3 / 22 | |
| 2.2.2 | 3 / 22 | |
| 2.2.1 | 3 / 22 | |
| 2.2.0 | 3 / 22 | |
| 2.1.5 | 3 / 22 | |
| 2.1.4 | 3 / 22 | |
| 2.1.3 | 3 / 22 | |
| 2.1.2 | 3 / 22 | |
| 2.1.1 | 3 / 22 | |
| 2.1.0 | 3 / 22 | |
| 2.0.12 | 3 / 22 | |
| 2.0.11 | 3 / 22 | |
| 2.0.10 | 3 / 22 | |
| 2.0.9 | 3 / 22 | |
| 2.0.7 | 3 / 22 | |
| 2.0.6 | 3 / 22 | |
| 2.0.5 | 3 / 22 | |
| 2.0.3 | 3 / 22 | |
| 2.0.2 | 3 / 22 | |
| 2.0.1 | 3 / 22 | |
| 2.0.0 | 3 / 22 |
v2.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Modified file contains 17 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Modified file contains 17 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Modified file contains 17 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
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.