Package evidence
@hanazuki/[email protected]
Install-time lifecycle script: install="cmake-js configure --CDCMAKE_EXPORT_COMPILE_COMMANDS=1 && cmake-js build"
Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["@hanazuki/[email protected]"],"fail_on":"high"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["@hanazuki/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
Install-time lifecycle script: install="cmake-js configure --CDCMAKE_EXPORT_COMPILE_COMMANDS=1 && cmake-js build"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk high · score 34 · status changed
Related candidates
Linked campaigns and clusters
Install-time lifecycle script — install="cmake-js configure --cdcmake_export_compile_commands=1 && cmake-js build"
2 members · evidence strength 56Install-time lifecycle script — install="cmake-js configure --CDCMAKE_EXPORT_COMPILE_COMMANDS=1 && cmake-js build"
2 members · evidence strength 56Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Install-time lifecycle script | package.json | install="cmake-js configure --CDCMAKE_EXPORT_COMPILE_COMMANDS=1 && cmake-js build" | 30 |
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Install-time lifecycle script | package.json | install="cmake-js configure --CDCMAKE_EXPORT_COMPILE_COMMANDS=1 && cmake-js build" | 30 |
| low | Install-time lifecycle script | package.json | prepare="if test -f ./scripts/apply-patches.sh; then ./scripts/apply-patches.sh; fi" | 4 |
Manifest
Package metadata
Scripts8
cmake-verbosecmake-js configure -l verbose --CDCMAKE_EXPORT_COMPILE_COMMANDS=1 --CDCMAKE_VERBOSE_MAKEFILE=1 && cmake-js build -l verbosecpplintcpplint --filter=-,+build,+runtime,-runtime/indentation_namespace src/*formatclang-format -i src/*installcmake-js configure --CDCMAKE_EXPORT_COMPILE_COMMANDS=1 && cmake-js buildprepareif test -f ./scripts/apply-patches.sh; then ./scripts/apply-patches.sh; fitestjasminetypetesttstyche --target '>=5.0'version./scripts/bump-version.cjs
Dependencies3
bindings^1.5.0cmake-js^8.0.0node-addon-api^8.5.0