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
- 175
- Versions published
- 5
- First published
- Jun 2026
- Publisher
- aditya-elastic
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":["[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":["[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
Scripts28
acceptance:universal-deepnode scripts/universal-deep-acceptance.mjsacceptance:universal-trustnode scripts/universal-trust-acceptance.mjsacceptance:web-qualitynode scripts/web-quality-acceptance.mjsbuildcross-env NODE_OPTIONS=--disable-warning=ExperimentalWarning next buildbuild:clinode scripts/build-cli.mjschecknpm test && npm run build:cli && npm run test:cli && npm run goal:audit && npm run acceptance:universal-trust && npm run acceptance:universal-deep && npm run trust:audit && npm run release:audit && npm run build && npm audit --audit-level=moderate && npm run package:dry-runcleannode -e "const fs=require('node:fs'); for (const dir of ['.next','.next-dev']) fs.rmSync(dir,{recursive:true,force:true})"devcross-env GAME_OS_NEXT_DIST_DIR=.next-dev NODE_OPTIONS=--disable-warning=ExperimentalWarning next devdev:freshnpm run clean && npm run devgoal:auditnode scripts/goal-audit.mjsgodot:playernode scripts/godot-player-agent.mjsgodot:smokenode scripts/godot-smoke.mjshomebrew:auditnode scripts/homebrew-audit.mjshomebrew:updatenode scripts/update-homebrew-formula.mjspackage:dry-runcross-env npm_config_cache=tmp/npm-cache npm pack --dry-runrelease:auditnode scripts/release-audit.mjssmokenode scripts/smoke-local.mjsstartcross-env NODE_OPTIONS=--disable-warning=ExperimentalWarning next starttestcross-env NODE_OPTIONS=--disable-warning=ExperimentalWarning vitest runtest:clinode scripts/cli-smoke.mjstest:watchcross-env NODE_OPTIONS=--disable-warning=ExperimentalWarning vitesttrust:auditnode scripts/trust-audit.mjsunity:advancednode scripts/unity-advanced-playtest.mjsunity:playernode scripts/unity-player-agent.mjsunity:smokenode scripts/unity-smoke.mjsvisual:smokenode scripts/visual-smoke.mjsweb:playernode scripts/web-player-agent.mjsweb:smokenode scripts/web-smoke.mjs
Dependencies2
playwright-core^1.60.0zod^3.24.1