@whalent/agent-core@0.3.515
⚠ Under reviewCore runtime for Whalent Agent
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest declares no lifecycle hooks, and inspected MCP code includes a platform-specific skill-file helper. The heavily obfuscated CLI bundle exceeds the inspection limit, so its behavior remains unresolved; manual review is appropriate.
Decision evidence
public snapshot- The manifest has no lifecycle hooks and points to a bundled CLI entrypoint.
- The inspected bundles use heavily obfuscated names and string-decoding wrappers; the CLI bundle exceeds the inspection limit, so its runtime behavior could not be fully resolved.
- The MCP bundle includes a helper that writes skill files beneath a platform-specific directory.
- The manifest declares no install-time script.
- The inspected skill helper performs file writes when called; the excerpts do not establish an automatic install-time trigger.
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.515.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.515 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.