@whalent/agent@0.3.452
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo registry-install lifecycle hook or concrete malicious behavior was found. The observed network authentication is activated through explicit runtime configuration.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and has no preinstall, install, or postinstall hook.
- The MCP runtime obtains its platform URL and token from caller-provided command-line arguments or Whalent environment settings.
- The runtime sends that supplied token as authorization to the configured platform API; no hidden default export destination was identified.
- Distributed JavaScript is heavily obfuscated, which reduces auditability.
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.452.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.452 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.