@whalent/agent-core@0.3.516
Core runtime for Whalent Agent
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe inspected code supports skill installation into agent configuration directories through a named tool, which leaves a concrete agent extension capability. It does not establish an automatic install-time attack, credential theft, or unrestricted file write.
Decision evidence
public snapshot- The named skill-management tool accepts an install action and slug, downloads the skill using the account token, and passes the returned files to the installer.
- The installer selects a scope-specific skill directory under the supported agent platform directories and writes downloaded files there.
- The writer resolves each file path beneath the selected skill directory and skips paths that escape it.
- The skill download helper uses the package’s configured service base and sends the account token to its skill endpoint.
- The manifest identifies the runtime entrypoints and contains no npm lifecycle scripts.
- The agent configuration change occurs through an explicit skill-management tool action; the inspected source does not show it running from an npm install hook.
- File-path checks constrain downloaded writes to the selected skill directory, and the package manifest has no lifecycle hook.
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-core@0.3.516.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.516 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.