@whalent/agent@0.3.497
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected package metadata and flagged bundle excerpts do not establish malicious behavior, and the manifest has no install-time lifecycle hook. Obfuscation reduces confidence, but the scanner's payload-loader signal is not proof of an active attack.
Decision evidence
public snapshot- The manifest declares a publish-time build hook, with no install-time lifecycle hook.
- The manifest identifies the package as a Whalent Agent runtime wrapper and lists agent protocol libraries as dependencies.
- The flagged URL fragment occurs in bundled schema-reference code; inspection did not establish a package-controlled payload loader or concrete attack behavior.
- The distributed entrypoints are heavily obfuscated, which limits behavioral review.
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.497.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.497 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.