@whalent/agent-core@0.3.526
⚠ Under reviewCore runtime for Whalent Agent
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install hook, and inspected MCP behavior does not establish an attack. The main executable exceeds the available verification limit, so its behavior cannot be resolved sufficiently to mark the package clean.
Decision evidence
public snapshot- package.json lists the CLI entrypoint and dependencies, with no lifecycle scripts.
- dist/mcp.cjs uses generated functions while compiling validators; the inspected excerpt does not establish remote payload execution.
- dist/mcp.cjs includes Cloudflare and Google DNS-over-HTTPS resolvers.
- The main executable exceeds the citation verifier’s 16 MiB limit, leaving its complete behavior unresolved.
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.526.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.526 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.