@whalent/agent@0.3.367
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package lacks an automatic installation trigger, but deliberate obfuscation of its active CLI prevents a dependable static determination of its capabilities. No source fact inspected proves an active attack.
Decision evidence
public snapshot- The package exposes dist/index.cjs as both its main module and CLI entrypoint.
- The active CLI bundle begins with an obfuscation wrapper, preventing reliable static verification of its process and network behavior.
- The manifest includes javascript-obfuscator as a development dependency, consistent with deliberate bundle obfuscation.
- package.json has no preinstall, install, or postinstall hook and no runtime dependency on its own package name.
- No concrete credential export, destructive action, or unconsented agent-configuration mutation was established from the inspected excerpts.
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.367.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.367 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.