@whalent/agent@0.3.364
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe entrypoint is intentionally opaque, creating unresolved runtime risk, but the inspected metadata contains no automatic installation trigger and no concrete malicious action was proven.
Decision evidence
public snapshot- The published CLI entrypoint is heavily JavaScript-obfuscated, preventing reliable static verification of its runtime behavior.
- Package metadata exposes the obfuscated file as both the main module and the whalent command.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- No concrete exfiltration endpoint or confirmed destructive action was established from the bounded inspection.
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.364.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.364 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.