@lovrabet/rabetbase-cli@2.5.7
Developer CLI for Lovrabet apps, datasets, pages, SQL, Backend Function, database connections, skills, and AI agent workflows.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe install hook automatically requests global installation of the package's own agent skill, creating an agent-extension lifecycle risk. The inspected source does not establish foreign control-surface abuse or a payload loader, so this warrants a warning rather than a publication block.
Decision evidence
public snapshot- The package defines a postinstall hook, and its wrapper calls the local postinstall routine.
- The postinstall routine invokes the built-in skill installer without a user choice check.
- That installer passes the package's bundled skill to a global skills installation command.
- The skill identifies itself as this package's Lovrabet development skill.
- The flagged routing and SQL files expose routing profiles and SQL normalization behavior; the inspected excerpts show no payload execution.
- The automatic global setup is for the package's own skill, which is aligned with the CLI's stated purpose.
- The inspected flagged routing and SQL excerpts do not establish an obfuscated payload loader.
Source & flagged code
5 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 dynamic require/import behavior.
scripts/postinstall.mjsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @lovrabet/rabetbase-cli@2.5.7.
See all versions of @lovrabet/rabetbase-cli for other recorded verdicts.
- Review the evidence and your use of @lovrabet/rabetbase-cli@2.5.7 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.