llm-wiki-loop@1.3.1
The production framework for self-improving & self-organizing LLM knowledge vaults — grounding invariants, code drift detection, auto-skillification, and 1-click multi-agent setup.
AI Security Review
scanned 22d ago · by lpm-firewall-aiAutomatic deployment and replacement of an agent extension creates a concrete lifecycle risk. The writes are restricted to the package-owned wiki-manager skill, supporting a warning rather than a malicious verdict.
Decision evidence
public snapshot- package.json automatically runs scripts/install.js after installation.
- scripts/install.js recursively copies the bundled wiki-manager extension and overwrites existing files in its destination.
- The installer targets detected global or project agent skill directories without a consent prompt.
- bin/cli.js also exposes skill installation and vault initialization through explicit user commands.
- Installer writes are confined to the package-owned wiki-manager extension rather than broad agent configuration.
- No credential export, remote payload execution, obfuscation, or runtime self-dependency was identified in the inspected entrypoints.
Source & flagged code
7 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.
bin/cli.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to llm-wiki-loop@1.3.1.
See all versions of llm-wiki-loop for other recorded verdicts.
- Review the evidence and your use of llm-wiki-loop@1.3.1 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.