github Rust analyzed 6822487

crlome/runar-forge

github

Persistent, semantically-searchable memory and a symbol-level code graph for AI coding agents. One static Rust binary — SQLite or PostgreSQL, MCP-compatible.

maintainer
crlome
licence
MIT
first seen
2026-08-02
last seen
2026-08-12
releases · 30d
1
short id
risk 42/100 · heuristic grade
C elevated inferred analyzer v33 (current)
  • capability exposure inferred + 14
  • recent drift inferred + 12
  • tool safety inferred + 19
  • trust mitigators mixed − 3

inferred mixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

grade last moved 4h ago · see ecosystem CVEs →

risk trajectory 3 movements
  • C · 50 C · 42
  • C · 51 C · 50
  • C · 43 C · 51
capability exposure grade factor +14
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 3 findings · grade factor +19
  1. high dangerous code

    committed secret: GitHub fine-grained PAT

  2. medium toxic flow (lethal trifecta)

    lethal trifecta reachable across this server's tools: private-data access + untrusted-content ingestion + network exfil

  3. low exfiltration combo

    sensitive read and network capabilities split across this server's tools

skills & danger signals github-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed commit 6822487 · analyzer v33 · 6d ago

skills & prompt files 1

danger signals1

other grade factors evidence elsewhere
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:crlome/runar-forge/badge.svg)](https://mcpobservatory.com/servers/github:crlome/runar-forge/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of crlome.