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
- 14
- Versions published
- 17
- First published
- Mar 2026
- Publisher
- mueidmursalinrifat
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
Scripts2
startnode index.jstestecho "Error: no test specified" && exit 1
Dependencies20
@noble/curves^2.2.0@noble/hashes^2.2.0@signalapp/libsignal-client0.70.0axios^1.8.4bluebird^3.7.2chalk^4.1.2cheerio^1.0.0-rc.10duplexify^4.1.3form-data^4.0.0gradient-string^2.0.2https-proxy-agent^4.0.0mime^3.0.0mqtt^4.3.8npmlog^1.2.0protobufjs^8.4.0request^2.53.0sequelize^6.37.6sqlite3^5.1.7totp-generator^1.0.0ws^8.18.1