The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.
Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Geometric theory of quantum error correction knowledge base with 117-paper index and DeepSeek RAG AI.
- Index of 12 volumes and 117 papers on quantum error correction
- DeepSeek RAG knowledge AI integration
- Open WebUI support for conversational access
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).
The level reads L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
3 samples (roughly every 5 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 10-05 · 3 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
Only 2 points (< 3): no chart yet
09-23 → 10-05 · 2 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
Verification & Compatibility◼ Ecosystem app
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
| plugin \ dsh | dsh 0.1.7-rc.2 | dsh 0.1.7-alpha.1 | dsh 0.1.6-alpha.2 | dsh 0.1.6-alpha.1 | dsh 0.1.5-rc.2 |
|---|---|---|---|---|---|
| v0.1.3 | · | · | · | · | ◼ |
v0.1.3github◼ 3 ecosystem app2026-09-30
https://github.com/sdoygb/conjugate-spectral-geometry
◼dsh 0.1.5-rc.22026-09-11Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/sdoygb/conjugate-spectral-geometry#v0.1.3
ID: conjugate-spectral-geometry@v0.1.3@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.3-alpha.22026-09-08Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/sdoygb/conjugate-spectral-geometry#v0.1.3
ID: conjugate-spectral-geometry@v0.1.3@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.3-alpha.12026-09-07Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/sdoygb/conjugate-spectral-geometry#v0.1.3
ID: conjugate-spectral-geometry@v0.1.3@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/conjugate-spectral-geometry/?ref=badge)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static high; dynamic medium (authoritative when present) → overall medium.
—v0.1.3git2026-10-07v0.1.3same versionsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalpipeShell · shell
linux/geometry-ai-server_1.0.0.90_amd64/usr/local/geometry-ai/install_openwebui.sh:13curl -fsSL https://get.docker.com | bash - warningnetIp · network
linux/geometry-ai-server_1.0.0.90_amd64/usr/local/geometry-ai/install_openwebui.sh:16docker run -d -p 8080:8080 --name geometry-webui \ --restart unless-stopped \ -e OPENAI_API_BASE_URL=http://172.17.0.1:5000/v1
show 3 audit findings
- mediumInstaller pipes remote Docker bootstrap script directly into bash without integrity check
linux/geometry-ai-server_1.0.0.90_amd64/usr/local/geometry-ai/install_openwebui.sh:13If get.docker.com, DNS, or the local TLS path is compromised, arbitrary code runs with the invoker's privileges (Docker installation normally requires root/sudo). Same script then pulls and runs the mutable 'ghcr.io/open-webui/open-webui:main' tag, so the executed image content can change after review. Reachable only when a user runs the script and answers the interactive prompt with '1'.
- lowZenodo API token read from a plaintext file placed alongside the scripts
zenodo_tools/check_token.py:7Three scripts (check_token.py, diagnose_api.py, diagnose_token.py) expect a long-lived Zenodo bearer token in clear text in the script directory, so it can be committed or shipped with the package. In these files the token is only sent to https://zenodo.org (its legitimate owner) and never printed, so no exfiltration was found; the residual risk is credential-at-rest exposure.
- lowZhihu session state (login cookies) stored in plaintext JSON next to publishing scripts
zhihu_publish/check_edit_state.py:8The Playwright scripts authenticate to zhuanlan.zhihu.com / zhihu.com/creator using a reusable storage_state.json containing the user's session cookies. Anyone who can read that file, or who receives the packaged/committed directory, obtains the logged-in Zhihu session. The scripts themselves only navigate to zhihu.com URLs and print page text, so no exfiltration channel was found.
Warn: bundled installer pipes a remote Docker script to bash, and helper scripts keep API tokens/session cookies in plaintext next to the code; the core plugin server code was not in the harvested set.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-09-04 · activity: Stable
• Repo created: 2026-08-18
• Stars: ★ 2 · Forks: 0
• Health: Stable — committed within 90 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is conjugate-spectral-geometry?
conjugate-spectral-geometry is an ecosystem app listed on dsh.so, not a DSH plugin package: it cannot be installed with dsh plugin add and ships through the project's own release channel.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install conjugate-spectral-geometry?
This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. The security scan still runs, but the L1-L5 plugin install ladder does not rate it.
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-10-17 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.
