@whalent/agent@0.3.379
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo malicious lifecycle hook or verified secret-exfiltration path was found, but the opaque executable contains high-impact agent-management and update functionality that cannot be adequately audited from this release.
Decision evidence
public snapshot- dist/index.cjs is deliberately obfuscated into a single opaque line while retaining child-process, filesystem, update, persistence, and npm-install logic.
- The CLI performs automatic wrapper/core update and supervision actions when the user runs whalent.
- README text claims the daemon accepts remote commands and starts configured workers; this is a broad agent-control capability.
- package.json has no preinstall, install, or postinstall hook; its only lifecycle script is prepublishOnly.
- The package’s executable behavior is activated through the whalent CLI, not package installation or import.
- The Python sidecar is a Jupyter RPC kernel helper and its visible code has no network client or credential collection.
Source & flagged code
5 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/index.cjsView on unpkg · L1Package source references dynamic require/import behavior.
dist/index.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @whalent/agent@0.3.379.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.379 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.