keyring-agent-core@0.3.1
Core AI chat agent with multi-agent architecture, ReAct pattern, and modular tool system powered by Gemini
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe suspicious metadata literals are part of a bundled URL-safety blocklist, and apparent .exec calls are regular-expression use. Source inspection found no malicious execution, harvesting, persistence, or install hook.
Decision evidence
public snapshot- Runtime chat functionality sends requests to configured Gemini/Keyring endpoints.
- Native bundle contains cloud-metadata host literals, but in a URL-safety denylist.
- package.json has only prepublishOnly; no install lifecycle hook.
- No child-process import, shell execution, eval, or payload loader found.
- No filesystem harvesting, persistence, or AI-agent control-surface writes found.
- Network use aligns with documented AI and blockchain-agent features.
Source & flagged code
5 flagged · loading sourcePackage source references child process execution.
dist/index.native.jsView on unpkg · L676A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.native.jsView on unpkg · L676Findings
Affected versions and remediation
This report applies to keyring-agent-core@0.3.1.
See all versions of keyring-agent-core for other recorded verdicts.
- Review the evidence and your use of keyring-agent-core@0.3.1 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.