github re-analysis due no deep scan

compiler-explorer/compiler-explorer

github

Compile code with thousands of compilers, inspect the assembly, and share godbolt.org links

maintainer
compiler-explorer
licence
first seen
2026-08-18
last seen
2026-08-18
releases · 30d
0
short id
risk 21/100 · heuristic grade
B low inferred analyzer v33 (current)
  • vulnerabilities attested + 7
  • capability exposure inferred + 22
  • trust mitigators mixed − 8

attested 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 1w ago · see ecosystem CVEs →

risk trajectory 1 movements
  • A · 14 B · 21
capability exposure grade factor +22
Inferred surface — each links to servers holding it:
vulnerabilities 1 CVEs · grade factor +7
MEDIUM
Persistent DOM-based XSS via unsanitized GoldenLayout labels affects ["< gh-18392"]
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
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:compiler-explorer/compiler-explorer/badge.svg)](https://mcpobservatory.com/servers/github:compiler-explorer/compiler-explorer/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 compiler-explorer.