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
- 388
- Versions published
- 6
- First published
- May 2026
- Publisher
- dreaktor
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":["@booga/[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":["@booga/[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
Scripts6
buildtsup && node scripts/copy-templates.mjs && node scripts/build-demo-dist.mjs && node scripts/build-compose-dist.mjsdevtsup --watchlinteslint .shape-historybun run scripts/history-shape/index.tstestvitest run --coveragetypechecktsc --noEmit
Dependencies18
@booga/vblocks^0.4.0@booga/vbrand^0.4.0-alpha.2@booga/vdsl^0.3.0@booga/vfixtures^0.1.1@booga/vlint^0.1.0@booga/vregistry^0.1.0@booga/vssg^0.1.0@booga/vtheme^0.3.0@booga/vui^0.4.0chalk^5.3.0commander^12.1.0execa^8.0.1fs-extra^11.2.0glob^10.4.5open^10.1.0ora^7.0.1prompts^2.4.2zod^3.23.8