@whalent/agent-core@0.3.495
⚠ Under reviewCore runtime for Whalent Agent
AI Security Review
scanned 19d ago · by lpm-firewall-aiDirect inspection established agent configuration capabilities but did not resolve their consent and activation paths through the heavily obfuscated CLI. Clipped source access and the entrypoint's citation verification size limit prevent a defensible clean or malicious determination.
Decision evidence
public snapshot- package.json points both the main entrypoint and CLI to dist/index.cjs; the inspected manifest contains no lifecycle hooks or runtime self-dependency.
- The flagged MCP location selects agent platform directories, including .cursor.
- dist/mcp.cjs contains a helper that modifies Codex MCP configuration in config.toml.
- dist/index.cjs dispatches tool requests to downloaded skill installation, but obfuscated activation and consent remain unresolved; source access was clipped and citation verification rejected its size.
- No concrete credential theft, malicious payload execution, or automatic npm install mutation was established.
- The inspected dynamic Function construction belongs to schema validation code.
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.495.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.495 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.