channel-worker@2.5.121
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 8d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected runtime behavior is package-aligned: it starts the worker on command and supports same-package updates and local NST discovery. Scanner indicators of shell execution, networking, and environment use did not establish concrete attack behavior in the inspected source.
Decision evidence
public snapshot- The manifest defines only start and dev commands and no install lifecycle hook.
- The CLI starts the daemon from an explicit start command using saved or supplied configuration.
- The updater checks npm for a newer release and installs the channel-worker package itself; the daemon starts this checker every five minutes.
- The new NST locator runs Windows-only process and port lookups to find the configured agent.
- The automatic updater can install newer releases globally, but source shows it retrieves the version for this same package from the npm registry.
- The shell calls in the NST locator are used for Windows process and port discovery; no unrelated command or remote payload behavior was identified.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
bin/cli.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to channel-worker@2.5.121.
See all versions of channel-worker for other recorded verdicts.
- Review the evidence and your use of channel-worker@2.5.121 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.