keyring-agent-core@0.3.10
Core AI chat agent with multi-agent architecture, ReAct pattern, and modular tool system powered by Gemini
AI Security Review
scanned 29d ago · by lpm-firewall-aiStatic inspection shows a Gemini multi-agent library whose entrypoints only export constructors and helpers. Install hooks, process execution, and covert exfiltration are absent, and the embedded vector default is used only when the caller enables that knowledge base.
Decision evidence
public snapshot- package.json version 0.3.10 sets main to dist/index.js and react-native to dist/index.native.js, with scripts limited to build, lint, test, and prepublishOnly build and no preinstall, install, or postinstall hook.
- dist/index.js exports AgentCore and DeFi/wallet tools, creates an axios client, and does not spawn processes, eval code, or run network calls at module load.
- dist/index.native.js is the React Native bundle entry and contains no child_process usage or install-time execution.
- Both bundles fall back to a vendor Upstash Vector REST URL and token only when UpstashKnowledgeBase is constructed or AgentCore is given vectorKB.enabled.
Source & flagged code
5 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 · L681Source 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.3.10.
See all versions of keyring-agent-core for other recorded verdicts.
- Review the evidence and your use of keyring-agent-core@0.3.10 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.