@whalent/agent-core@0.3.528
⚠ Under reviewCore runtime for Whalent Agent
AI Security Review
scanned 12h ago · by lpm-firewall-aiThe manifest has no install-time hooks, and the inspected MCP operations appear to be explicitly invoked tools. The 16 MiB obfuscated CLI bundle remains unresolved, so the evidence does not support either a clean or malicious verdict.
Decision evidence
public snapshot- The package exposes a command-line entrypoint through dist/index.cjs.
- The MCP bundle contains platform actions that update profiles and goals, and it can start a daemon MCP server when run directly.
- The primary CLI bundle is heavily obfuscated and exceeds the citation verifier’s size limit, so its behavior could not be resolved from the inspected excerpts.
- package.json declares no lifecycle scripts, so installation does not automatically run the CLI or MCP server.
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.528.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@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.