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.
- Weekly downloads
- 196
- Versions published
- 7
- First published
- Jun 2026
- Publisher
- ladamczyk
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@ladamczyk/[email protected]"],"fail_on":"review"}'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":["@ladamczyk/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
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 low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts2
buildrimraf ./bin && rollup -c rollup.bin.js --silent && rollup -c rollup.config.js --silent && chmod +x ./bin/qoq.jsdevnpm run build && node ./bin/qoq.js
Dependencies12
@antfu/install-pkg1.1.0@eslint/compat2.1.0@ladamczyk/qoq-utils^4.2.3@npmcli/package-json7.0.5cac7.0.0cosmiconfig9.0.2es-toolkit1.47.0micromatch4.0.8picocolors1.1.1prompts2.4.2react-fast-compare3.2.2semver7.8.4