keyring-agent-core@0.3.18
Core AI chat agent with multi-agent architecture, ReAct pattern, and modular tool system powered by Gemini
AI Security Review
scanned 23d ago · by lpm-firewall-aiInspected behavior is consistent with an AI and wallet agent library, with caller-configured authentication and UI-producing wallet actions. Static inspection established no concrete malicious chain warranting a warning or publication block.
Decision evidence
public snapshot- The manifest selects JavaScript and native entrypoints and contains no install lifecycle hooks or runtime self-dependency.
- The native Gemini client takes its API key from caller configuration and defaults to Google's API or the Keyring Gemini proxy.
- Gemini requests send chat contents and the configured API key through the client's request method.
- Wallet action code builds UI component properties rather than signing or broadcasting transactions.
- Targeted inspection found no shell execution, dynamic code evaluation, or private-key harvesting in either entrypoint.
Source & flagged code
4 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 · L684Source 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.18.
See all versions of keyring-agent-core for other recorded verdicts.
- Review the evidence and your use of keyring-agent-core@0.3.18 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.