xuzhougeng/ScientificFigureLibrary
C3Local-first MCP App for scientific figures. Import, review, and publish a global library on disk; reuse exact templates in Pi, DeepSeek Harness (dsh), Claude, Codex, Cursor, and Wisp.
★ 100+ · xuzhougeng/ScientificFigureLibrary source on GitHub · this plugin in the registry
xuzhougeng/ScientificFigureLibrary is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, decodes base64 payloads, starts a network server.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./.dsh-plugin/cordis.patch.yml |
| executes system commands | exec | ×9 in authored code, e.g. src/github-publication-tools.ts:4, src/github-publication-tools.ts:295 |
| decodes base64 payloads | base64_decode | ×9 in authored code, e.g. src/candidate-images.ts:44, src/lifecycle-tools.ts:874 |
| starts a network server | net_server | ×4 in authored code, e.g. src/index.ts:31, src/server.ts:17 |
| reads credential-class env vars in development tooling the package does not ship | token_env_tooling | in development tooling the package does not ship: SFL_OPEN_FIGURE_ED25519_PRIVATE_KEY_BASE64 |
Tool registrations
0 static tool registration point(s).
Services it injects
skills
Outbound domains
xuzhougeng.github.io api.github.com developers.openai.com code.claude.com modelcontextprotocol.io pi.dev deepseek-harness.github.io
Environment variables it reads
FIGUREYA_SOURCE_PACK_DIR PERSONAL_MODULE_SOURCE_PACK_DIR ComSpec SFL_DIAGNOSTICS_DIR LOCALAPPDATA XDG_DATA_HOME FIGURE_WORKSPACE_DIR FIGUREYA_ASSETS_DIR FIGUREYA_ARCHIVE_BASE_URLS SFL_MCP_UPDATE_NOTICES
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.