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
- 192
- Versions published
- 36Established · −30% score
- First published
- Oct 2025
- Publisher
- ghoshbishakh
Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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
Scripts20
buildtsupbuild:tsctscbumpnode scripts/bumpVersion.js --bump && npm installbump:majornode scripts/bumpVersion.js --bump --major && npm installbump:minornode scripts/bumpVersion.js --bump --minor && npm installdevnpm link @pinggy/pinggy && npm run build && npm linkpack:allnpm run pack:linux-x64 && npm run pack:linux-arm64 && npm run pack:win-x64 && npm run pack:macos-x64 && npm run pack:macos-arm64pack:linuxnpm run pack:linux-x64 && npm run pack:linux-arm64pack:linux-arm64npm run pre-pkg && pkg . --targets node20-linux-arm64 --output out/pinggy-linux-arm64 && npm run post-pkgpack:linux-x64npm run pre-pkg && pkg . --targets node20-linux-x64 --output out/pinggy-linux-x64 && npm run post-pkgpack:macosnpm run pack:macos-x64 && npm run pack:macos-arm64pack:macos-arm64npm run pre-pkg && pkg . --targets node20-macos-arm64 --output out/pinggy-macos-arm64 && npm run post-pkgpack:macos-x64npm run pre-pkg && pkg . --targets node20-macos-x64 --output out/pinggy-macos-x64 && npm run post-pkgpack:win-arm64npm run pre-pkg && pkg . --targets node20-win-arm64 --output out/pinggy-win-arm64.exe && npm run post-pkgpack:win-x64npm run pre-pkg && pkg . --targets node20-win-x64 --output out/pinggy-win-x64.exe && npm run post-pkgpack:windowsnpm run pack:win-x64 && npm run pack:win-arm64post-pkgnode scripts/pre_pkg_processing.js restorepre-pkgnode scripts/pre_pkg_processing.js removestartnode dist/index.jstestnode --experimental-vm-modules node_modules/jest/bin/jest.js
Dependencies9
@pinggy/pinggy^0.4.6blessed^0.1.81clipboardy^5.0.0mime^4.1.0picocolors^1.1.1qrcode^1.5.4winston^3.17.0ws^8.18.0zod^4.1.5