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
- 12
- First published
- Mar 2026
- Publisher
- mueidmursalinrifat
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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
Remote Payload: matched "raw.githubusercontent.com"
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 review · score 12 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Payload | package/checkUpdate.js | matched "raw.githubusercontent.com" | 12 |
Manifest
Package metadata
Scripts2
startnode index.jstestecho "Error: no test specified" && exit 1
Dependencies14
axios^1.8.4bluebird^3.7.2chalk^4.1.2cheerio^1.0.0-rc.10duplexify^4.1.3gradient-string^2.0.2https-proxy-agent^4.0.0mqtt^4.3.8npmlog^1.2.0request^2.53.0sequelize^6.37.6sqlite3^5.1.7totp-generator^1.0.0ws^8.18.1