channel-worker@2.5.130
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 flagged runtime behaviors are consistent with the package's worker update and Windows agent-location functions. The updater is a residual supply-chain risk, but the inspected source does not establish an attack or an unrelated recipient for credentials.
Decision evidence
public snapshot- The manifest exposes the CLI and daemon; its scripts are limited to start and dev, with no lifecycle hook.
- The agent username comes from the CLI argument or saved local configuration.
- The updater checks the matching package on the npm registry and installs that package when a newer version is available.
- The daemon starts the periodic updater as part of its runtime.
- The locator uses the configured username to filter Windows process listings and identify the Nstbrowser agent.
- The daemon can automatically install a newer package release from the registry.
- The locator interpolates the configured username into a shell command; the inspected caller takes it from CLI or saved configuration.
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.130.
See all versions of channel-worker for other recorded verdicts.
- Review the evidence and your use of channel-worker@2.5.130 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.