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
- 108
- Versions published
- 12
- First published
- Apr 2026
- Publisher
- ramuyk
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":["@inteli.city/[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":["@inteli.city/[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
Scripts 1
Sign in to view install / lifecycle script contents.
Dependencies21
body-parser1.20.3content-type1.0.5cookie0.7.2cookie-parser1.4.7cors2.8.5form-data4.0.4got12.6.1hash-sum2.0.0hpagent1.2.0is-utf80.2.1jsonwebtoken^9.0.2jwks-rsa^3.1.0media-typer1.1.0multer2.0.2mustache4.2.0nunjucks^3.2.4on-headers1.1.0raw-body3.0.0tough-cookie5.1.2uuid9.0.1zod^3.23.8