@whalent/agent-core@0.3.505
Core runtime for Whalent Agent
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest declares no lifecycle scripts, and the inspected MCP dispatch is request-driven. Heavy obfuscation in the shipped MCP bundle leaves unresolved behavior, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The manifest points its CLI at dist/index.cjs and declares no lifecycle scripts.
- The MCP bundle uses heavily obfuscated identifiers and control flow.
- The MCP bundle dispatches named tool requests to tool handlers; the inspected excerpt does not establish a malicious action.
- No install-time lifecycle hook is declared.
- The inspected MCP excerpt shows tool handlers invoked through named requests.
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-core@0.3.505.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.505 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.