github not analyzable

roman10/mcode

github

Tiling IDE for macOS to manage multiple Claude Code sessions in parallel

maintainer
roman10
license
Apache-2.0
first seen
2026-06-10
last seen
2026-06-10
releases · 30d
1
short id
risk insufficient evidence

Insufficient evidence to grade. This server's source has not been statically analyzed, so a low grade would only mean "nothing found", not "nothing there". We don't show a reassuring grade we can't stand behind. Attested signals (CVEs, provenance) below still apply.

Once the source is analyzed (see the analysis flag in the header), a graded score appears here. How analysis works: methodology.

graded 14m ago · see ecosystem CVEs →

risk trajectory 1 movements
  • A · 0B · 32
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

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

analyzed analyzer v19 · 10h ago

skills & prompt files 2

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:roman10/mcode/badge.svg)](https://mcpobservatory.com/servers/github:roman10/mcode/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 roman10.