channel-worker@2.5.56
Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
Channel Manager worker daemon — runs on remote machines to execute video pipeline jobs
AI Security Review
scanned 1mo ago · by lpm-firewall-aiLifecycle hooks are absent, and the daemon, browser jobs, and npm self-update start only after an explicit CLI command with a worker token. Those behaviors match the stated channel-worker product and do not show a concrete hidden attack.
Decision evidence
public snapshot- package.json exposes only start and dev scripts and has no preinstall, install, or postinstall hook.
- The start command loads a local config and exits unless a worker token is already present.
- The updater queries the public npm registry for this same package name and installs a newer global release only after the user-started daemon is running.
- A running daemon checks for a newer channel-worker release every five minutes and can npm-install it globally, then restart.
- After an explicit pair or init, the process polls the configured dashboard and drives browser profile jobs.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
bin/cli.jsView on unpkg · L2The start command loads a local config and exits unless a worker token is already present.
bin/cli.jsView on unpkg · L110Findings
Affected versions and remediation
This report applies to channel-worker@2.5.56.
See all versions of channel-worker for other recorded verdicts.
- Review the evidence and your use of channel-worker@2.5.56 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.