@hap-toolkit/chrome-devtools-frontend
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
zsl369evilemontech_bro_in_vivodiydyq
Keywords
devtoolschromechromiumblinkdebugger
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in bundled Chrome DevTools Runtime.js — expected pattern for the DevTools module loader. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is in a Vue Router vendor bundle (chunk-vendors.js) — standard template engine pattern. | ai | |
| phantom-deps | phantom-dep:sync-directory | AI (phantom-deps): sync-directory is declared as a runtime dep and referenced in config; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.1.2 | 1 / 0 |
v1.1.2
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.