What it does
GitHub/Gitea (and other forge) accounts with project-scoped grants and push policy for DSH better-sidebar. Tokens stay in DSH_HOME, not model context.
Installation
dsh plugin --profile web add github:thirsty5034/dsh-git-forgeInstall method: GitHub · not yet tested in container (L3+)
Compatibility
| DSH Version | Status |
|---|---|
| not stated | Declared — not tested |
Requirements
- • Node.js: not stated
- • DSH: declared "not stated"
- • External credentials: none detected
Security Report
Automated static scan, not manual review.
Critical findings in non-blocking categories (dynamic code execution, shell execution, install scripts, obfuscation). Common in CLI/terminal plugins but worth reviewing.
code-exec ×10.1.4dsh manifest8660cb60cd992026-08-198660cb60cd99The scan result is only valid for the scanned commit. If the latest commit differs, the badge shows outdated until the daily pipeline rescans.
Disclaimer: automated static analysis, not a security guarantee. Always review what you install.
• Static heuristic scan: done (12 files)
• Dependency vulnerabilities: requires deep audit (L3+)
• Permission sandboxing: requires runtime testing (L4+)
High-risk findings · 3 / 3
- criticalChild process module usage (Node.js)lib/shared/remote-resolve.js:5import { spawnSync } from 'node:child_process'
- warningFilesystem write operationsscripts/install.sh:147if (t !== before) fs.writeFileSync(p, t);
- warningFilesystem write operationsscripts/install.sh:204fs.writeFileSync(p, out.join("\\n").replace(/\\n{3,}/g, "\\n\\n"));
Heuristic static scan — may produce false positives. Review the source yourself before trusting.
Activity
Last commit 2026-08-18 · activity: Active
• Repo created: 2026-08-19
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
