geml-spec/geml
C3One format, two readers. People and AI agents now co-write the same document. Legible for people; addressable, verifiable, and versioned for machines. GEML is plain text — organized by one typed bloc
★ 10+ · geml-spec/geml source on GitHub · this plugin in the registry
geml-spec/geml is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, starts a network server, reads credential-class env vars.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×68 in authored code, e.g. integrations/test-all.mjs:22, integrations/test-all.mjs:101 |
| starts a network server | net_server | ×1 in authored code, e.g. geml-parser/codemap/serve.mjs:443 |
| reads credential-class env vars | token_env | LOGSEQ_API_SERVER_TOKEN |
Outbound domains
cdn.jsdelivr.net docs.joern.io marketplace.visualstudio.com
Environment variables it reads
LOGSEQ_CLI_DIR GEML_TRUST_STORE GEML_OUT GEML_CLI CLAUDE_PROJECT_DIR GEML_JOERN GEML_GRAPH_DIR XDG_CONFIG_HOME GEML_WATCH_QUIET_MS GEML_WATCH_TREE
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.