@whalent/agent@0.3.520
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package declares no install lifecycle hook, and its prepublishOnly script only invokes a build. Obfuscated bundles and an agent skill-writing capability leave an unresolved integration question, but the inspected source does not establish an active attack.
Decision evidence
public snapshot- The package exposes a CLI entrypoint whose bundled source begins with an obfuscated loader.
- The MCP bundle includes code that resolves skill destinations across machine, project, and managed scopes, then creates directories and writes skill files; the inspected excerpt does not establish the caller's consent or full activation path.
- The only publish lifecycle hook shown runs a build command; no install lifecycle hook is declared.
- Skill installation appears to be package functionality in the MCP bundle, but the inspected excerpts do not establish an unconsented lifecycle trigger or a broader control-surface mutation.
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.520.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.520 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.