@whalent/agent@0.3.453
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic global self-update is a concrete supply-chain capability but does not prove a current malicious payload. The absence of install hooks in this release makes blocking unsupported.
Decision evidence
public snapshot- The CLI checks for a newer wrapper release during normal execution.
- The wrapper invokes a global npm installation of the selected wrapper version.
- The published manifest has no install lifecycle hook; its only lifecycle-like script is prepublishOnly.
- The examined update code uses a non-shell child-process call.
- No current package install hook or direct credential-exfiltration sink was identified.
Source & flagged code
7 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/mcp.cjsView on unpkg · L1A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/mcp.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @whalent/agent@0.3.453.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.453 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.