@whalent/agent@0.3.501
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 12d ago · by lpm-firewall-aiObfuscation in the shipped executable and MCP bundle prevents reliable tracing of their behavior, leaving a real unresolved runtime risk. The inspected source does not establish a concrete attack or a malicious lifecycle chain, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The CLI entrypoint is heavily obfuscated, preventing reliable static tracing of its behavior.
- The MCP bundle is also obfuscated; a visible CLI configuration uses Whalent’s platform host and accepts a token argument.
- The manifest identifies a build script that can disable obfuscation, but the published entrypoint remains obfuscated.
- The manifest has no preinstall, install, or postinstall hook; its only publish lifecycle hook is prepublishOnly.
- The visible MCP CLI configuration points to the package’s Whalent platform host.
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.501.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.501 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.