@whalent/agent@0.3.508
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe skill-management feature is activated through an MCP tool request, and the manifest has no npm install hook. Because it can add remote skill content to machine or workspace agent directories, this warrants a warning as a first-party agent extension capability.
Decision evidence
public snapshot- The flagged MCP location resolves agent-specific directories; nearby code supports machine and workspace skill locations.
- An incoming MCP tool call can request a skill download and installation using a selected slug, platform URL, and bearer token.
- The installer writes returned skill files beneath the resolved directory and rejects paths outside that directory.
- The manifest's prepublishOnly hook runs the build; no install hook is declared.
- The skill installation is activated through an MCP tool request, not an npm lifecycle hook.
- The source shows a first-party skill-management feature, with no evidence that the downloaded content is automatically executed.
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@0.3.508.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.508 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.