keyring-agent-core@0.3.9
Core AI chat agent with multi-agent architecture, ReAct pattern, and modular tool system powered by Gemini
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe undisclosed credentialed backend creates a concrete runtime data-disclosure risk, but it is gated behind consumer-enabled knowledge-base operations and no install-time execution was found.
Decision evidence
public snapshot- The runtime bundle hard-codes an Upstash endpoint and uses it when vector credentials are absent.
- The vector client silently falls back to a bundled token, then can upload caller-provided knowledge-base entries.
- The public types say credentials fall back to environment variables, which does not disclose the bundled service fallback.
- package.json has only a prepublish build hook, so registry installation does not run package code.
- Knowledge-base upload requires vector mode and either auto-ingest or an explicit ingestion call.
- No package-owned child-process or cloud-metadata access was confirmed; the metadata strings are SSRF-blocking rules in bundled dependencies.
Source & flagged code
5 flagged · loading sourcePackage source references child process execution.
dist/index.native.jsView on unpkg · L681A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.native.jsView on unpkg · L681Findings
Affected versions and remediation
This report applies to keyring-agent-core@0.3.9.
See all versions of keyring-agent-core for other recorded verdicts.
- Review the evidence and your use of keyring-agent-core@0.3.9 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.