github Go not analyzable deep scan unknown

stackql/stackql

v0.11.669
github

not analyzable — repository too large to scan in full

Query, provision and operate Cloud, SaaS, API and Model Context Protocol (MCP) resources through a unified SQL-based framework for humans and AI agents.

maintainer
stackql
licence
MIT
first seen
2026-06-16
last seen
2026-09-09
releases · 30d
6
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.

risk trajectory 8 movements
  • B · 18 A · 6
  • B · 26 B · 18
  • C · 38 B · 26
  • A · 14 C · 38
  • B · 26 A · 14
  • A · 10 B · 26
  • B · 22 A · 10
  • A · 0 B · 22
capability exposure grade factor +22
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.

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