loragent@2.0.0
108-agent virtual software firm for Lorapok Labs — includes orchestration, image generation, GIF creation, deployment, development, business, and design agents. Hub-and-Spoke topology with MCP lazy-loading and crash recovery.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic postinstall performs broad, consentless writes to user and project AI agent configuration surfaces, including MCP settings and agent rules. This meets the install-time control-surface blocking criterion.
Decision evidence
public snapshot- The package postinstall script automatically runs the universal sync routine.
- That routine rewrites MCP configuration in user and project directories, including adding the package's server and remote MCP entries.
- It copies package skills into global agent directories and writes agent rules and Roo Code modes into the project.
- The configured MCP server exposes agent steering and CLI execution tools, making these settings behavior-bearing.
- The sync behavior is consistent with installing Loragent's own agent tooling, and the inspected code shows no credential collection or exfiltration in this path.
- The shell alias installer is a separate script and is not invoked by the package lifecycle hook.
- The secret-looking values in the lifecycle test are synthetic scanner test inputs.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage contains a critical-looking secret pattern.
tests/lifecycle-hooks.test.jsView on unpkg · L66Findings
Affected versions and remediation
This report applies to loragent@2.0.0.
See all versions of loragent for other recorded verdicts.
- Avoid installing loragent@2.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.