Fisfzy/dsh-typwriter

C3

★ 0 · Fisfzy/dsh-typwriter source on GitHub · this plugin in the registry

Fisfzy/dsh-typwriter is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, runs code at install time, executes commands in development tooling the package does not ship, uses eval in development tooling the package does not ship.

Installable plugin — declares a dsh.bundle manifest

What it can do

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./cordis.patch.yml
runs code at install timeinstall_scriptpreinstall: npx only-allow pnpm; postinstall: pnpm -r --if-present sync
executes commands in development tooling the package does not shipexec_tooling×13 in development tooling the package does not ship, e.g. apps/texpile-editor/scripts/capture-lang-fixtures.mjs:13, apps/texpile-editor/scripts/capture-lang-fixtures.mjs:13
uses eval in development tooling the package does not shipeval_tooling×4 in development tooling the package does not ship, e.g. apps/texpile-editor/scripts/gen-typst-symbols.mjs:92, apps/texpile-editor/scripts/gen-typst-symbols.mjs:108
decodes base64 in development tooling the package does not shipbase64_decode_tooling×1 in development tooling the package does not ship, e.g. apps/texpile-editor/scripts/gen-typst-symbols.mjs:261
starts a network server in development tooling the package does not shipnet_server_tooling×1 in development tooling the package does not ship, e.g. apps/texpile-editor/scripts/audit-typst-corpus.mjs:33

Tool registrations

0 confirmed registration point(s); analysis is incomplete.

3516 source file(s) omitted by size/count/encoding limits; tool count is incomplete

Outbound domains

texpile.com discord.gg arxiv.org join.texpile.com

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.