@whalent/agent-core@0.3.488
Core runtime for Whalent Agent
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection supports a warning for unresolved executable behavior in heavily obfuscated bundles, with the main entrypoint exceeding the inspection tool's size limit. The inspected functionality and manifest do not establish a block-eligible attack.
Decision evidence
public snapshot- The executable bundles obscure identifiers and strings, leaving runtime behavior unresolved after bounded inspection.
- dist/index.cjs contains obfuscated child-process calls; its size exceeds the source tool's inspection and citation verification limit.
- package.json has no lifecycle scripts or runtime self-dependency.
- The inspected dynamic function construction belongs to bundled schema compilation, not a demonstrated hidden payload loader.
- The MCP startup accepts command-line configuration and a token; no covert credential export was established.
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.488.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.488 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.