@whalent/agent-core@0.3.466
Core runtime for Whalent Agent
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe package can write foreign agent skill directories, but only after an explicit skills tool call, not from an npm lifecycle hook. That is a guarded agent-configuration capability, so it warrants a warning rather than a publish block.
Decision evidence
public snapshot- package.json exposes bin whalent-core to dist/index.cjs and has no install lifecycle scripts.
- dist/mcp.cjs platformDir maps Claude platforms to .claude and Cursor platforms to .cursor.
- A tool handler downloads skill files with an Authorization header and calls installSkill using the caller platform.
- installSkill creates the resolved skill directory recursively and writes skill files there.
- Dependencies are ssh2 plus optional node-pty, not a self-referential release chain.
- No preinstall, install, or postinstall hook runs this write during npm install.
- Skill installation is inside an explicit tool switch, not module top-level 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.466.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.466 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.