PkgRadar

Package evidence

@jaimevalasek/[email protected]

Remote Payload: matched "api.telegram.org/bot"

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
19
First published
Mar 2026
Publisher
jaimevalasek

Recommended action

Review before promoting

Mixed 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":["@jaimevalasek/[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":["@jaimevalasek/[email protected]"],"fail_on":"review"}'
Publisherjaimevalasek
Artifact bytes2,368,396
Previous version1.18.0
Published2026-05-28T01:49:18.897Z
SHA-256d8a0ebaa6470355755bd1af3951d5731142ec46ee620ef1e696e27c80f8db630

Why flagged

What the scanner saw

Remote Payload: matched "api.telegram.org/bot"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
27Score
1.19.0Version
Status history (2 events)
  1. availableavailable · risk review · score 27 · status available -> available, risk high -> review, score 62 -> 27
  2. newavailable · risk high · score 62 · status changed

Evidence

Static findings

4 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
mediumRemote Payloadpackage/src/mcp-connectors/registry.jsmatched "api.telegram.org/bot"12
Show all 4 findings (low-signal and informational)
SeverityKindPathDetailPoints
mediumRemote Payloadpackage/src/mcp-connectors/registry.jsmatched "api.telegram.org/bot"12
lowCredential file accesspackage/src/lib/git-commit-guard.jsmatched "aws_access_key"5
lowMessenger Bot Endpointpackage/src/mcp-connectors/registry.jsmatched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)5
lowCredential file accesspackage/src/lib/security/secrets-regex.jsmatched "id_rsa"5

Manifest

Package metadata

Scripts8
  • cinpm run lint && npm test
  • lintnode --check src/*.js src/commands/*.js src/i18n/*.js src/i18n/messages/*.js bin/*.js
  • sync:agentsnode src/commands/sync-agents-preflight.js && rsync -av --progress --exclude='config.md' --exclude='runtime/' --exclude='backups/' --exclude='mcp/servers.local.json' template/ ./
  • testnode --test
  • test:genomenode --test tests/genome-compat.test.js tests/genome-migrate.test.js
  • test:genome-2.0-smokenode scripts/smoke/genome-2.0-smoke.js
  • test:genome-2.0:block-anode scripts/smoke/genome-2.0-smoke.js && npm run test:genome && npm test && npm run lint
  • test:genome-2.0:rolloutnode scripts/testing/genome-2.0-rollout.js
Dependencies3
  • archiver^8.0.0
  • better-sqlite3^12.6.2
  • terser^5.48.0