@whalent/agent@0.3.368
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found a user-invoked CLI entry point and no registry install lifecycle trigger. Obfuscation warrants caution but does not by itself establish an active attack.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and contains no install lifecycle hook.
- The executable entry point is a Node CLI file rather than an install-time script.
- The CLI bundle is heavily obfuscated, which limits transparency, but no concrete malicious behavior was identified in the inspected entry path.
Source & flagged code
5 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/index.cjsView on unpkg · L1Package source references dynamic require/import behavior.
dist/index.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @whalent/agent@0.3.368.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.368 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.