@whalent/agent@0.3.514
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package exposes heavily obfuscated runtime bundles, and static inspection did not resolve their behavior well enough to establish a concrete attack. The manifest shows only a build-time prepublishOnly hook and declares an obfuscation tool, so the evidence supports a warning rather than a publish block.
Decision evidence
public snapshot- The package exposes dist/index.cjs as its main entry point and three CLI commands.
- The shipped entry point and MCP bundle begin with opaque string-table decoder code, which limits review of their runtime behavior.
- The manifest lists a JavaScript obfuscation tool as a development dependency, so the obfuscation may be intentional.
- The only manifest lifecycle hook is prepublishOnly, which runs the build script.
- The manifest does not show a preinstall, install, or postinstall hook; its prepublishOnly hook runs a build command.
- The manifest’s obfuscation dependency offers a benign explanation for the opaque output, but does not resolve what the shipped code does.
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.514.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.514 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.