volcengine/OpenViking
C3Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
★ 28k+ · volcengine/OpenViking source on GitHub · this plugin in the registry
volcengine/OpenViking is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, runs code at install time, gates tool execution, executes system commands.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| runs code at install time | install_script | postinstall: node bin/postinstall.mjs |
| gates tool execution | tool_gate | hook: tools/pre-execute |
| executes system commands | exec | ×8 src, e.g. npm/cli/bin/ov.mjs:2, npm/cli/bin/ov.mjs:2 |
| reads credential-class env vars | token_env | AUTH_DIR, BRIDGE_TOKEN, OPENVIKING_API_KEY, OPENVIKING_BEARER_TOKEN |
Services it injects
agents sessions tools
Hooks it attaches
agent/pre-step agent/session-start session/event session/flush tools/pre-execute
Outbound domains
docs.openviking.ai example.feishu.cn swagger.io
Environment variables it reads
OPENVIKING_URL OPENVIKING_BASE_URL OPENVIKING_BEARER_TOKEN OPENVIKING_API_KEY OPENVIKING_ACCOUNT OPENVIKING_USER OPENVIKING_PEER_ID OPENVIKING_TIMEOUT_MS OPENVIKING_DEBUG_LOG OPENVIKING_CLI_CONFIG_FILE
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.