@whalent/agent-core@0.3.519
⚠ Under reviewCore runtime for Whalent Agent
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe inspected manifest has no lifecycle hook, and the reviewed agent skill writes occur through explicit MCP tool requests. The heavily obfuscated primary entrypoint prevents resolving the package’s full behavior, so further review is warranted without a confirmed attack finding.
Decision evidence
public snapshot- The manifest names dist/index.cjs as the package entrypoint and declares no lifecycle scripts.
- The skill-management handler downloads and installs files only when its action is install; the MCP request handler routes requested tools to that logic.
- The flagged helper maps skill locations to supported agent directories, and writes are constrained to paths under the selected skill directory.
- The primary CLI bundle is exceptionally large and heavily obfuscated, so its complete runtime behavior remains unresolved.
- The manifest declares no install-time lifecycle hook.
- The inspected skill installation flow is reached through an MCP tool request and an explicit install action.
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.519.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.519 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.