keyring-agent-core@0.2.62
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 fixed fallback endpoint and remote query path create a real conditional data-disclosure risk. The explicit feature gate and absence of install hooks do not support blocking publication.
Decision evidence
public snapshot- The main bundle embeds a fixed Upstash Vector endpoint and uses it when neither configuration nor environment supplies a URL.
- When vectorKB is enabled, the package creates that vector client and sends each search input as query data to it.
- The React Native bundle contains the same conditional vector-client setup and query sink.
- The manifest has only a prepublish build hook, not an install-time hook.
- Vector storage is conditional on the caller enabling vectorKB, and the caller can provide a URL and token.
- No automatic install-time execution, shell execution, metadata retrieval, or local-file harvesting was found in the inspected entrypoints.
Source & flagged code
7 flagged · loading sourceA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.native.jsView on unpkg · L675Source reaches cloud instance metadata or link-local credential endpoints.
dist/index.native.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to keyring-agent-core@0.2.62.
See all versions of keyring-agent-core for other recorded verdicts.
- Review the evidence and your use of keyring-agent-core@0.2.62 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.