@whalent/agent-core@0.3.453
Core runtime for Whalent Agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no automatic lifecycle hook, so there is no confirmed install-time attack. Its unusually opaque, daemon-capable agent runtime accepts credentials and cannot be sufficiently traced by static inspection, warranting a non-blocking warning.
Decision evidence
public snapshot- The package exposes dist/index.cjs as both its main entry point and CLI executable.
- The MCP executable accepts a platform URL and token configuration when directly run.
- The main executable is heavily obfuscated and contains daemon PID and replacement-intent logic, preventing reliable static tracing of its privileged behavior.
- package.json declares no npm lifecycle scripts.
- No direct credential transmission, destructive action, or foreign AI-agent configuration mutation was confirmed from the inspected source.
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.453.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.453 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.