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
- 159
- First published
- Jan 2026
- Publisher
- itsmuzin
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
Scripts1
buildtsc && copyfiles -u 1 "src/**/*.{vue,d.ts}" dist
Dependencies20
@rollup/plugin-alias^6.0.0@rollup/plugin-commonjs^29.0.2@rollup/plugin-json^6.1.0@rollup/plugin-node-resolve^16.0.3@rollup/plugin-replace^6.0.3@rollup/plugin-terser^0.4.4@vue/server-renderer^3.5.34chokidar^3.6.0commander^14.0.3esbuild^0.27.7esbuild-plugin-vue3^0.5.1koffi^2.16.2rollup^4.60.3rollup-plugin-esbuild^6.2.1rollup-plugin-vue^6.0.0sharp^0.34.5ts-loader9.5.4ts-node^10.9.2typescript^5.9.3ws^8.20.0
Optional dependencies3
@fastify/cookie^11.0.2@fastify/formbody^8.0.2cookie-parser^1.4.7