@whalent/agent@0.3.425
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe absence of install hooks rules out an automatic install-chain block. Deliberate obfuscation around CLI update and process-control behavior leaves a real unresolved runtime risk.
Decision evidence
public snapshot- The executable entry point is deliberately obfuscated, preventing normal audit of its runtime behavior.
- When the user runs the CLI, its main routine invokes a wrapper-update routine before supervising the core process.
- The CLI contains routines to run npm commands and check persistence context, creating an opaque update and process-management capability.
- package.json has no preinstall, install, postinstall, or prepare hook; its only lifecycle script is prepublishOnly.
- The risky wrapper logic is reached through the user-invoked whalent CLI, not package installation.
- No concrete credential theft, destructive action, or network endpoint was recoverable from the inspected source.
Source & flagged code
6 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 · L1The executable entry point is deliberately obfuscated, preventing normal audit of its runtime behavior.
dist/index.cjsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @whalent/agent@0.3.425.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.425 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.