@whalent/agent@0.3.380
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no automatic registry-install lifecycle hook, so a publish block is not justified. Its user-triggered global self-update and opaque executable create a real unresolved supply-chain risk that warrants a warning.
Decision evidence
public snapshot- The executable is deliberately string-obfuscated, including a runtime decoder, which prevents meaningful auditing of much of its behavior.
- Running the CLI automatically invokes a wrapper update routine that resolves a newer version and installs it globally with npm.
- The entrypoint also installs and supervises a separate core runtime, expanding the executable supply-chain surface.
- package.json has no preinstall, install, postinstall, or prepare hook; its only lifecycle-like script is prepublishOnly.
- The update behavior is reached from the user-invoked CLI entrypoint, not during package installation.
- No concrete credential theft, destructive action, or foreign AI-agent configuration write was confirmed from the inspected source.
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.380.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.380 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.