@hap-toolkit/debugger
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 |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is inside a webpack bundle using eval-source-map; contains hapjs-platform copyright header — standard build artifact. | ai | |
| phantom-deps | phantom-dep:koa | AI (phantom-deps): koa is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:webpack | AI (phantom-deps): webpack is a declared runtime dependency used as a bundler; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@jayfate/path | AI (phantom-deps): Declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.9 | 15 / 4 | |
| 2.0.8 | 15 / 4 | |
| 2.0.7 | 15 / 4 | |
| 2.0.6 | 15 / 4 | |
| 2.0.5 | 15 / 4 | |
| 2.0.4 | 15 / 4 | |
| 2.0.3 | 15 / 4 | |
| 2.0.2 | 15 / 4 |
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.8
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.4
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.