azwosile/dsh-tripo-studio

C3

★ 10+ · azwosile/dsh-tripo-studio source on GitHub · this plugin in the registry

azwosile/dsh-tripo-studio 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

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./cordis.patch.yml
executes system commandsexec×14 in authored code, e.g. plugin/scripts/install-local.mjs:7, plugin/scripts/install-local.mjs:7
decodes base64 payloadsbase64_decode×4 in authored code, e.g. plugin/server/credentials.js:29, plugin/server/credentials.js:51
starts a network servernet_server×30 in authored code, e.g. plugin/scripts/smoke-test.mjs:43, plugin/scripts/smoke-test.mjs:51
reads credential-class env varstoken_envTRIPO_CN_API_KEY, TRIPO_STUDIO_WEB_TOKEN

Tool registrations

0 static tool registration point(s).

Services it injects

webServer

Outbound domains

developers.tripo3d.com cdn.tripo3d.ai openapi.tripo3d.com developers.tripo3d.ai openapi.tripo3d.ai

Environment variables it reads

TRIPO_TEST_BROWSER APPDATA DSH_APP_NODE_MODULES TRIPO_CN_API_KEY TRIPO_TEST_FBX_FILE SystemRoot TRIPO_COMPAT_FIXTURES TRIPO_STUDIO_DATA_DIR TRIPO_CN_ENABLE_PAID TRIPO_ASSET_HOSTS

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.