PkgRadar

Package evidence

[email protected]

no findings

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
3
First published
Jun 2026
Publisher
yucekj

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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"}'
Publisheryucekj
Artifact bytes149,430
Previous version0.1.1
Published2026-06-05T03:53:07.524Z
SHA-2561177948b65904c59f8dbbaf91ad3c33539489c88df7d51a007efc0bc72bb3e20

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

low
Last checked
lowRisk
0Score
0.1.2Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts20
  • build:bridgenode scripts/build-bridge.mjs
  • build:bridge:allnode scripts/build-bridge.mjs --all
  • build:bridge:debugnode scripts/build-bridge.mjs --no-minify
  • check:im-runtime-health-matrixnode tools/im-runtime-health-matrix-check.mjs
  • check:runtime-status-contractnode tools/verify-runtime-status-contract.mjs
  • devtsx scripts/dev-server.ts
  • example:feishu-webhooktsx scripts/example-feishu-webhook.ts
  • example:iflow-agenttsx scripts/example-iflow-agent.ts
  • example:single-agenttsx scripts/example-single-agent.ts
  • localexport RESTART_ALL_EXIT_PROCESS="0" && export RUNTIME_CONFIG_PULL_URL="http://127.0.0.1:4999/api/v1/yucegpt/im/runtime/config/full" && export ENABLE_INTERNAL_API="1" && export INTERNAL_CONTROL_PORT="18999" && export INTERNAL_FIXED_TOKEN="syim_runtime" && export LOCAL_CONFIG_ONLY=1 && npm run start:bridges
  • remoteexport RESTART_ALL_EXIT_PROCESS="0" && export RUNTIME_CONFIG_PULL_URL="http://127.0.0.1:4999/api/v1/yucegpt/im/runtime/config/full" && export ENABLE_INTERNAL_API="1" && export INTERNAL_CONTROL_PORT="18999" && export INTERNAL_FIXED_TOKEN="syim_runtime" && npm run start:bridges
  • starttsx src/cli.ts start
  • start:bridgestsx bridges/main.ts
  • start:bridges:inspecttsx --inspect-brk bridges/main.ts
  • start:connectortsx src/connector-host.ts
  • start:dingtalktsx scripts/dingtalk-stream-server.ts
  • start:feishu-bridgetsx scripts/feishu-yuce-bridge.ts
  • start:lark-bridgetsx bridges/lark-stdio-bridge.ts
  • start:stdio-bridgetsx bridges/dingtalk-stdio-bridge.ts
  • start:stdio-bridge:bundlenode dist/dingtalk-stdio-bridge.cjs
Dependencies12
  • @ffmpeg-installer/ffmpeg^1.1.0
  • axios^1.6.0
  • dingtalk-stream^2.1.4
  • fluent-ffmpeg^2.1.3
  • form-data^4.0.0
  • mammoth^1.8.0
  • pdf-parse^1.1.1
  • tsx^4.21.0
  • ylib-dingtalk-connector0.7.11-1
  • ylib-openclaw-lark2026.3.18-1
  • ylib-openclaw-weixin2.1.8-1
  • ylib-wecom-openclaw-plugin2026.4.29-2