@whalent/agent-core@0.3.527
Core runtime for Whalent Agent
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install hooks, and the package description is consistent with an agent runtime. However, the obfuscated published MCP bundle prevents reliable verification of all runtime behavior, so the unresolved risk warrants a warning rather than a clean verdict or a claim of confirmed attack behavior.
Decision evidence
public snapshot- package.json points the command-line entrypoint at dist/index.cjs and declares no lifecycle scripts.
- dist/mcp.cjs uses a large encoded string table and its embedded metadata lists javascript-obfuscator, leaving runtime behavior difficult to verify from the published source.
- README.md describes the package as Whalent Agent’s core runtime, launched by its wrapper.
- The manifest has no preinstall, install, or postinstall hook.
- The README and manifest describe a package-aligned agent runtime and its executable entrypoint.
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.527.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.527 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.