@whalent/agent@0.3.495
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 19d ago · by lpm-firewall-aiInspected source supports a warning for runtime agent configuration capability, with no evidence establishing an unconsented npm install attack. Obfuscation and limited verification of the oversized core reduce confidence in broader conclusions.
Decision evidence
public snapshot- dist/core.cjs routes MCP tool requests to operations that install downloaded skills and register or remove MCP servers.
- dist/mcp.cjs resolves skill destinations under workspace or home agent directories and writes supplied files.
- dist/mcp.cjs can update MCP server entries in config.toml.
- package.json has no npm install hooks or runtime self-dependency; dist/index.cjs activates the core through CLI execution.
- No concrete covert credential export or malicious install-time mutation was established.
- Obfuscated bundles limit inspection; dist/core.cjs exceeded the citation tool's verification size limit.
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.495.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@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.