@whalent/agent@0.3.411
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install lifecycle hook or self-dependency supports a publish block. The deliberately opaque executable and its update capability warrant a warning until a readable artifact is supplied.
Decision evidence
public snapshot- The published CLI entry point is heavily obfuscated, making its filesystem and child-process behavior difficult to audit.
- The opaque wrapper contains update and npm-command routines that can run when a user launches the CLI.
- package.json has no preinstall, install, or postinstall hook.
- The package has no runtime dependency on its own package name.
- No eval or Function use was found in dist/index.cjs.
- The readable Python sidecar is a local Jupyter-kernel NDJSON helper.
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.411.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.411 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.