@whalent/agent-core@0.3.503
Core runtime for Whalent Agent
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged agent integration code resolves a skill directory and guards file paths before writing supplied skill files. Obfuscation limits assurance, but the inspected source does not establish an attack.
Decision evidence
public snapshot- package.json has no npm lifecycle hook and points to a runtime entrypoint.
- The flagged mcp code selects agent skill locations using the home directory and supplied platform settings.
- The skill writer checks resolved paths and skips unsafe file paths.
- The installer writes supplied skill files into the selected skill directory.
- The distributed bundles are heavily obfuscated, which limits confidence in static interpretation.
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.503.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.503 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.