@whalent/agent@0.3.459
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInstall does not execute package code, and the runtime host and sibling dependency match the stated Whalent agent CLI. Obfuscated process and Claude config helpers are part of that user-started agent, not an install hook or a hidden exfiltration chain.
Decision evidence
public snapshot- package.json names the CLI bin whalent as dist/index.cjs and its scripts are build, prepublishOnly, start, and test, with no preinstall, install, or postinstall hook.
- The published runtime identifies its service host as memory.whalent.com, matching the Whalent Memory CLI described by the package.
- optionalDependencies pins the sibling package @whalent/agent-core to the same version 0.3.459 and does not depend on this package name.
- Shipped bundles are obfuscated and contain child_process use plus writers for Claude MCP config, which execute only after the user launches the whalent command.
- new Function appears inside bundled schema code generation rather than an install-time payload.
Source & flagged code
7 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/mcp.cjsView on unpkg · L1A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/mcp.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @whalent/agent@0.3.459.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.459 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.