langchain-retrieval
Audited by Socket on Feb 21, 2026
1 alert found:
Malware[Skill Scanner] Destructive bash command detected (rm -rf, chmod 777) All findings: [CRITICAL] command_injection: Destructive bash command detected (rm -rf, chmod 777) (CI004) [AITech 9.1.4] [CRITICAL] command_injection: Destructive bash command detected (rm -rf, chmod 777) (CI004) [AITech 9.1.4] Based on the README fragment, this appears to be a legitimate RAG template using LangChain.js and Supabase pgvector. The notable supply-chain/security concerns are: unnecessary encouragement to use high-privilege secrets (SUPABASE_PRIVATE_KEY, SUPABASE_DB_URL) without guidance on limiting scope or storage; and an instruction to delete git history which may remove provenance. There is no direct evidence in this fragment of malicious code (exfiltration, reverse shell, obfuscated payloads). However, because no implementation code was provided, you should review server-side source files to confirm secrets are used only server-side, that network requests target official endpoints, and that sensitive values are not logged or forwarded. Recommend updating docs to: prefer least-privilege keys, use secret managers, avoid suggesting rm -rf .git without explanation, and explicitly state where service keys are required (e.g., migrations only). LLM verification: No definitive embedded malware was found in the provided documentation fragment. The primary issues are operational and supply-chain risks: requesting excessive credentials (SUPABASE_PRIVATE_KEY and direct DB URL), instructions to remove git history (reducing auditability), brittle file-moving commands, and lack of guidance for secret handling and dependency verification. Recommend: avoid providing service-role or direct DB credentials in .env for typical deployments; prefer least-privilege keys