channel-worker@2.5.110
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 source shows an automatic update path that passes an unvalidated registry-provided version into a shell command, creating conditional remote code execution risk. The updater targets this package through the fixed npm registry, so the source supports a warning rather than a publish block.
Decision evidence
public snapshot- The manifest has no install lifecycle hook; its scripts are explicit start and development commands.
- The updater reads the latest version field from the fixed npm registry endpoint.
- The daemon starts the periodic updater automatically after registration.
- The fetched version is interpolated into a shell command without visible validation as a safe package version.
- Starting the daemon requires a worker token.
- The updater targets this package itself through the fixed npm registry endpoint.
- The reviewed CLI requires a worker token before starting, and the manifest does not run an install hook.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
bin/cli.jsView on unpkg · L2Package source invokes a package manager install command at runtime.
lib/updater.jsView on unpkg · L29Findings
Affected versions and remediation
This report applies to channel-worker@2.5.110.
See all versions of channel-worker for other recorded verdicts.
- Review the evidence and your use of channel-worker@2.5.110 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.