@whalent/agent@0.3.500
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe source is heavily obfuscated and includes code for selecting agent configuration directories, leaving its behavior and consent flow unresolved. The available excerpts do not establish a concrete attack or an install-time mutation, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The published entrypoint is an obfuscated executable bundle, and its publish hook only runs a build.
- The flagged bundle maps agent platforms to home-directory configuration folders, but the inspected excerpt does not reveal the caller, consent flow, or configuration write.
- The manifest has no preinstall, install, or postinstall hook; its only publish lifecycle hook is prepublishOnly.
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.500.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.500 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.