PicGo/PicGo-Core
C2:zap:The ultimate image uploading engine. Both CLI & API supports.
★ 500+ · PicGo/PicGo-Core source on GitHub · this plugin in the registry
PicGo/PicGo-Core is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It executes system commands, decodes base64 payloads, reads credential-class env vars.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| executes system commands | exec | ×5 src, e.g. src/lib/PluginHandler.ts:218, src/utils/getClipboardImage.ts:2 |
| decodes base64 payloads | base64_decode | ×8 src, e.g. src/lib/ConfigSyncManager/E2ECryptoService.ts:51, src/lib/ConfigSyncManager/E2ECryptoService.ts:71 |
| reads credential-class env vars | token_env | CF_ACCESS_CLIENT_SECRET, PICGO_SERVER_SECRET |
Outbound domains
test.com cloud.tencent.com xxx.yyy.glb.clouddn.com xxx.test.upcdn.net developer.qiniu.com github.dev api.picgo.app cloud.picgo.app api.github.com api.imgur.com
Environment variables it reads
PICGO_VERSION VERSION PICGO_API_URL PICGO_CLOUD_URL ENABLE_PICGO_CLOUD_DEV_MODE CF_ACCESS_CLIENT_ID CF_ACCESS_CLIENT_SECRET PICGO_SERVER_SECRET PICGO_MOCK_LIFECYCLE
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.