PkgRadar

Package evidence

[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
282Mature · −50% score
First published
Jan 2018
Publisher
kikobeats

Effective trust discount applied: 50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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":["[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"}'
Publisherkikobeats
Artifact bytes14,886
Previous version3.10.1
Published2026-06-05T18:08:15.488Z
SHA-2563c7feceb5f6e60c2e9ed32fe8afccd28bdce174c9abed04f626e7eaa716e723c

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
5Score
3.10.2Version
Status history (1 event)
  1. newavailable · risk review · score 5 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumRemote Payloadpackage/src/commands/notification/telegram.jsmatched "api.telegram.org/bot"12
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
mediumRemote Payloadpackage/src/commands/notification/telegram.jsmatched "api.telegram.org/bot"12
lowMessenger Bot Endpointpackage/src/commands/notification/telegram.jsmatched "api.telegram.org/bot" — messenger-bot URL without exfil context (likely a notification handler)5

Manifest

Package metadata

Scripts15
  • buildgulp build && untracked > .vercelignore
  • cleanrm -rf node_modules
  • contributors(npx git-authors-cli && npx finepack && git add package.json && git commit -m 'build: contributors' --no-verify) || true
  • coveragec8 report --reporter=text-lcov | coveralls
  • devsvr src/router
  • dev:docsconcurrently "gulp" "npm run dev:docs:server"
  • dev:docs:serverbrowser-sync start --server --files "index.html, README.md, static/**/*.(css|js)"
  • lintstandard
  • postreleasenpm run release:tags && npm run release:github && (ci-publish || npm publish --access=public)
  • pretestnpm run lint
  • releasegit-authors-cli && git add package.json && standard-version -a
  • release:githubgithub-generate-release
  • release:tagsgit push --follow-tags origin HEAD:master
  • starttom
  • testNODE_ENV=test c8 ava
Dependencies32
  • @kikobeats/time-span~1.0.11
  • @lukeed/ms~2.0.2
  • acho~4.0.6
  • beauty-error~1.2.21
  • cors~2.8.5
  • got~11.8.6
  • helmet~8.2.0
  • http-body~1.0.17
  • http-compression~1.1.2
  • import-modules~2.1.0
  • is-buffer~2.0.5
  • joycon~3.1.1
  • lodash~4.18.1
  • mailgen~2.0.32
  • map-values-deep~1.0.2
  • meow~9.0.0
  • mitt~3.0.1
  • morgan~1.11.0
  • nodemailer~8.0.0
  • ow~0.28.2
  • p-reflect~2.1.0
  • p-retry~4.6.1
  • p-waterfall~2.1.1
  • picocolors~1.1.1
  • pupa~2.1.1
  • req-country~1.2.14
  • request-ip~3.3.0
  • router-http~2.0.1
  • send-http~1.0.6
  • stripe22
  • …and 2 more.