@whalent/agent-core@0.3.511
⚠ Under reviewCore runtime for Whalent Agent
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the inspected agent configuration code does not show an attack. Because the obfuscated main entrypoint could not be fully reviewed, the package requires manual review.
Decision evidence
public snapshot- The manifest names dist/index.cjs as the package entrypoint; inspection found an obfuscated bootstrap, and the file exceeded the available source inspection limit.
- The indicated MCP code also uses obfuscated identifiers, leaving some agent integration behavior difficult to trace.
- The manifest contains no lifecycle scripts.
- The inspected MCP code maps agent platforms to local configuration directories; this alone does not establish an attack.
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.511.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.511 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.