@whalent/agent@0.3.433
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo automatic install hook or concrete exfiltration behavior was found, but the opaque executable has broad local execution capability. This warrants a warning rather than publication block.
Decision evidence
public snapshot- The published CLI entry point is heavily obfuscated, preventing meaningful audit of its runtime behavior.
- The obfuscated entry point imports filesystem, operating-system, and child-process functionality and starts a daemon when the CLI runs.
- The package includes a Jupyter sidecar that starts a Python kernel, adding code-execution capability.
- package.json has no preinstall, install, or postinstall hook; its only lifecycle script is prepublishOnly.
- No fixed network endpoint or explicit credential-exfiltration path was recoverable from the static source.
- The Python sidecar is readable and its kernel launch is part of its stated runtime role.
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.433.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.433 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.