@whalent/agent@0.3.449
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe absence of install hooks reduces supply-chain risk, but the executable entrypoint cannot be meaningfully audited because it is deliberately obfuscated. A warning is warranted for unresolved active-code risk, not a block.
Decision evidence
public snapshot- The package exposes dist/index.cjs as both its main module and the whalent command.
- The active entrypoint is heavily obfuscated, including a rotating string-array decoder, preventing reliable static tracing of its privileged runtime behavior.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- package.json does not declare a runtime dependency on its own package name.
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.449.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.449 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.