loragent@2.0.1
224-agent virtual software firm for Lorapok Labs — Hub-and-Spoke topology, 6 squad formations, TiTi Vault zero-trust enclave, MCP lazy-loading, and autonomous multi-agent orchestration.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe postinstall hook automatically writes MCP configuration and installs skills into global agent directories. This meets the blocking policy for unconsented install-time mutation of a broad AI-agent control surface.
Decision evidence
public snapshot- package.json runs `npm run sync` from its postinstall hook.
- scripts/universal-sync.js merges MCP server definitions and installs Loragent into users’ MCP configuration files.
- The sync script copies package skills into global skill directories, including agent tooling locations.
- scripts/generate-artifact.js writes Cursor rules when invoked for artifact generation.
Source & flagged code
16 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 source references child process execution.
bin/loragent-email.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to loragent@2.0.1.
See all versions of loragent for other recorded verdicts.
- Avoid installing loragent@2.0.1. 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.