@whalent/agent@0.3.439
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no automatic npm install hook, so the evidence does not establish an install-time attack. Its opaque, automatic global self-update capability is nevertheless a meaningful supply-chain risk that warrants a warning.
Decision evidence
public snapshot- Package metadata exposes the bundled wrapper as both the main module and the whalent executable.
- The executable unconditionally invokes its wrapper update check before supervising the core runtime.
- The update path installs a selected version of the wrapper package globally through a child-process call.
- The distributed entry bundle is deliberately obfuscated, preventing transparent auditing of the update and execution path.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The update behavior is activated when the wrapper runs, rather than during npm installation.
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.439.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.439 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.