@whalent/agent-core@0.3.512
Core runtime for Whalent Agent
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package has no install hook, and the inspected skill setup is an explicit runtime capability. Because it can place fetched content in agent skill directories, residual agent extension setup risk warrants a warning rather than a block.
Decision evidence
public snapshot- The manifest declares the runtime entry point and no install lifecycle hook.
- The MCP source maps agent skills to platform directories and supports machine, workspace, and agent scopes.
- The installer creates the selected skill directory and writes supplied files there.
- The skill downloader requests files from the Whalent service using an authorization header.
- The observed skill setup is an explicit runtime operation, not an npm install hook.
- The inspected source establishes no credential theft, destructive action, or remote code execution.
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.512.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.512 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.