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.
- Versions published
- 8
- First published
- Jun 2026
- Publisher
- alquist42
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":["@nwire/[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":["@nwire/[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
Scripts8
buildvue-tsc -b && vite builddevvitepreviewvite previewstorybookstorybook dev -p 6006storybook:buildstorybook buildtest:e2eplaywright testtest:unitvitest runtypecheckvue-tsc --noEmit
Dependencies19
@nwire/supervisor0.12.1@tailwindcss/vite^4.0.0@vitejs/plugin-vue^5.2.1@vue-flow/background^1.3.2@vue-flow/controls^1.1.2@vue-flow/core^1.42.5@vue-flow/minimap^1.5.3@vueuse/core^11.3.0class-variance-authority^0.7.1clsx^2.1.1elkjs^0.11.1lucide-vue-next^0.469.0monaco-editor^0.55.0reka-ui^2.5.1tailwind-merge^2.6.0tailwindcss^4.0.0vitenpm:rolldown-vite@latestvue^3.5.13vue-router^4.5.0