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.

@songgms/dsh-git-graph avatar

@songgms/dsh-git-graph

Ecosystem appDeveloperGitHub integrationCode review
Verification
L5 · Ecosystem app
Risk
Out of scope
Health
Stable
Trust
Silver

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

A sidebar panel that draws your repo's Git commit graph, refs, commit details and per-file diffs beside the conversation.

  • SVG commit graph with branch lanes, newest first, one colour per branch
  • Shows local branches, remotes and tags as refs
  • Commit details and per-file diffs in the same window
developerAIgithubAIcode-reviewAI

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

GitHub repository

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.

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

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
◼ Ecosystem app
At-a-glance → evidence in the cards below
plugin \ dshprehistory
7ba25e✓
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
7ba25egithub✓ 1 runtime-verified2026-10-05

https://github.com/songgms/dsh-git-graph

✓prehistory2026-10-05L5 · runtime verified
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: unknown
  • • Plugin artifact: github · https://github.com/songgms/dsh-git-graph (version unstated)
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Unknown
L5 runtime
Passed
Install + runtime smoke verified in the dsh sandbox — installs and runs
L5 · runtime verified · valid for prehistory

ID: dsh-git-graph-6@7ba25e@dshunknown · profile: l4-sandbox

Issued: 2026-10-05 · expires: 2026-10-12

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-09-30
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-09-30
L4 · Install tested? Unknown
Sandbox install verdict? Unknown
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-05
spec github:songgms/dsh-git-graph · channel GitHub source · outcome unknown
L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-01
spec github:songgms/dsh-git-graph · install mode reused L4 scratch
check took: 374ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-10-01
ready line dsh web: http://127.0.0.1:64095/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-10-01
path / · HTTP 200 · took 374ms
Plugin active in inventory✓ Passed
Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-01
verdict active · entries 150
match: include:git-graph · dsh-git-graph · phase active
phases: active 122 · null 28

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

Author badges

Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-git-graph-6.svg)](https://www.dsh.so/artifact/dsh-git-graph-6/?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.

dsh-git-graph-6Automated review · daily

Static low; dynamic medium (authoritative when present) → overall medium.

static low→dynamic medium→overall medium
dynamic findings0 critical·0 high·1 medium·2 low
mediumoverall · medium
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.1.0dsh manifest
scanned version0.1.0git2026-10-07
current version0.1.0same version
vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

show static findings (3)
  • criticaldestructiveRm · destructivetools/verify-host.mjs:273

    await readCommit({ repo, hash: 'HEAD; rm -rf /' });

  • warningshellExec · shelllib/git.js:75

    execFile('git', args, {

  • warningnewFunction · code-exectools/check-client.mjs:60

    new Function('require', 'window', body);

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-16
audited artifactgit cc2f42a40f545b81c638121f1935c1c94c3dd0c1
findings0 critical·0 high1 medium / 2 low hidden
show 3 audit findings
  • mediumreadLog passes caller-supplied ref verbatim as a git option (no `--`, no revision guard)lib/git.js:612

    `request.ref` is appended to the `git log` argv with no `--` separator and no revision validation (unlike readCommit at line 634, which rejects metacharacters). A caller value such as `--output=/home/user/.bashrc` is interpreted by git as an option (`git log --output=<file>` writes the log to that path), giving arbitrary-path file write/clobber with the log text as content; if the opened repository's commit messages are attacker-influenced (e.g. a cloned untrusted repo), part of that content is attacker-controlled. Reachability depends on lib/routes.js forwarding the raw ref, which was not har

  • lowreadDiff validates the path but not the hash passed to gitlib/git.js:699

    Only the path is screened; `hash` reaches the argv unvalidated. `revision(hash)` appends the literal `^{commit}` (unless already present), so an injected option must end with `^{commit}` (e.g. `--output=/tmp/x^{commit}`); the primitive is therefore partially constrained but still an option-injection gap in a path the sibling function deliberately guards. Reachability depends on the unharvested route layer.

  • lowModule header claims all git calls are read-only while the file exports destructive operationslib/git.js:6

    The claim is factually false for this file: it exports pullRepo, pushRepo, stashSave/stashPop/stashDrop, resetToCommit (`reset --hard`), resetSoft, cherryPick, rebaseOnto, checkoutBranch, mergeBranch/mergeCommit, deleteBranch and createRef. A reviewer or policy engine relying on the header could grant the plugin blanket git access with no approval/confirmation surface, which is exactly what the comment argues for.

Static 'critical' refuted: git runs via execFile argv (no shell); tools/ is dev-only. Real gap: readLog/readDiff pass unvalidated revisions to git, enabling option injection if routes forward them.

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-10-01 · activity: Stable

• Repo created: 2026-09-29

• Stars: ★ 1 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/songgms/dsh-git-graph

Frequently asked questions

What is @songgms/dsh-git-graph?

@songgms/dsh-git-graph 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 @songgms/dsh-git-graph?

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-16 (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.

Was this page helpful?