@whalent/agent@0.3.528
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 11h ago · by lpm-firewall-aiThe package has no install-time lifecycle hook, and the inspected dynamic-code match is consistent with bundled proxy resolution. The main CLI remains substantially obfuscated, leaving enough unresolved runtime risk to warrant a warning rather than a clean verdict or a block.
Decision evidence
public snapshot- The published CLI entrypoint is heavily obfuscated, including a decoder that reconstructs strings at runtime, which limits review of its behavior.
- The CLI contains code that runs npm commands to retrieve package version information; its full behavior is difficult to assess in the obfuscated bundle.
- The manifest lists only a publishing-time build hook, not an install-time hook.
- The dynamic function construction found in the MCP bundle is inside bundled PAC resolver code, consistent with evaluating proxy configuration; it does not establish a payload loader.
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.528.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.528 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.