FylarOpen/dsh-fylar-office-editor
C2Office document preview, editing, and DOCX generation for DeepSeek Harness, powered by Fylar Office SDK.
★ 100+ · FylarOpen/dsh-fylar-office-editor source on GitHub · this plugin in the registry
FylarOpen/dsh-fylar-office-editor is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, executes commands in development tooling the package does not ship, eval in build output only.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can rewrite the system prompt | prompt_surface | systemPrompt, webServer |
| executes commands in development tooling the package does not ship | exec_tooling | ×9 in development tooling the package does not ship, e.g. scripts/smoke-dsh-install.mjs:1, scripts/smoke-dsh-install.mjs:1 |
| eval in build output only | eval_bundled | ×10 in build output only, e.g. vendor/office-sdk/lib/worker/wasm/bootloader.js:10, vendor/office-sdk/lib/worker/wasm/bootloader.js:74 |
Services it injects
fs locale sandboxPolicy sidebarRight sidebarRightTabs slots systemPrompt tools uiConversation webServer workspaceRegistry
Outbound domains
schemas.openxmlformats.org schemas.microsoft.com openlicense.fylar.ai
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.