github TypeScript not analyzable deep scan unknown

dork-labs/dorkos

github

not analyzable — repository too large to scan in full (large monorepo)

You, multiplied. Mission control for Claude Code, Codex, and OpenCode: see every session, approve what your agents do, and run them on a schedule. Self-hosted, MIT.

maintainer
dork-labs
licence
MIT
first seen
2026-06-06
last seen
2026-09-10
releases · 30d
10
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 7 movements
  • C · 44 B · 32
  • C · 52 C · 44
  • C · 57 C · 52
  • D · 69 C · 57
  • C · 49 D · 69
  • B · 32 C · 49
  • A · 0 B · 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 1 findings · grade factor +5
  1. medium toxic flow (lethal trifecta)

    lethal trifecta reachable across this server's tool + source surface: private-data access + untrusted-content ingestion + network exfil (a leg is proven only in the analyzed source)

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