Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it doesAI
A self-evolving programming cognitive kernel with 27 domain packages, an experience library, and an engineering toolchain for DeepSeek Harness.
- 27 domain packages covering broad programming topics
- 55 RFB experience library for proven practices
- Engineering toolchain with business, security, and evolution systems
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
dsh plugin --profile web add github:ljc6413/pkg-dev#v1.1.0Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| v1.1.0 | ○ | ○ | ○ | ○ | ○ |
v1.1.0github○ 11 ecosystem plugin2026-10-18
https://github.com/ljc6413/pkg-dev
○dsh 0.2.1-rc.2current2026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.2.1-alpha.42026-10-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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.2.1-alpha.22026-10-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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.2.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.2.0-rc.12026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.6-alpha.12026-09-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
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.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/ljc6413/pkg-dev#v1.1.0
ID: pkg-dev@v1.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/pkg-dev/)`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 low, dynamic medium — stricter wins → overall medium.
v1.1.0v1.1.0git2026-10-21v1.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalshellExec · shell
server-dashboard/ops-snapshot.mjs:28try { return execSync('sudo cat /var/log/nginx/access.log 2>/dev/null', { encoding: 'utf8', timeout: 20000 }).split('\n') } catch { return [ - warningfsWrite · files
server-dashboard/ops-snapshot.mjs:187fs.writeFileSync(OUT, JSON.stringify(snap, null, 2), 'utf8')
show 4 audit findings
- mediumnpm postinstall silently sends hostname and OS to a third-party endpoint without consent
tools/postinstall-report.mjs:12Every `npm install @yihe/pkg-dev` automatically executes the script, which POSTs the machine hostname, OS, package version and a timestamp to an external domain controlled by the vendor. There is no opt-out, no consent prompt and no mention in the package metadata; the only user-visible trace appears on success. Hostnames are routinely identifying in corporate environments.
- lowbootstrap-install.mjs phones home at module load, including for --dry-run
bootstrap-install.mjs:114The installer CLI (bin yihe-pkg-install) sends the hostname/OS/version before any user-visible action; even the explicitly non-mutating `--dry-run` preview triggers the outbound request. Same data class as the postinstall finding, reachable via a documented command.
- lowCron script shells out with sudo to read nginx logs (fixed string, no injection)
server-dashboard/ops-snapshot.mjs:28The static scanner's 'critical' flag is not reproduced: the command is a hard-coded literal with no interpolated input, and the file is neither a npm `bin` nor part of package.json `files`, so it never runs on an installing user's machine. Residual risk is operational only — the script assumes a pre-configured sudoers rule for the log path and writes a snapshot (with masked license keys and buyer names) to /opt/yihe-server/data for the /api/ops dashboard.
- lowLicense keys are generated and validated entirely client-side, so any user can mint enterprise keys
tools/key-issue.mjs:41genKey derives keys purely from crypto.randomBytes with no server-side secret, and validateKey accepts any string matching the shape regex. Because the generator ships as a public bin, any end user can run `yihe-pkg-key --tier ent` and produce a syntactically valid enterprise key, defeating the commercial tier gating the plugin advertises.
Install-time telemetry silently POSTs hostname/OS to a third-party endpoint; other scanner flags are fixed-command and client-side licensing, not RCE.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-05 · activity: Stable
• Repo created: 2026-08-29
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/ljc6413/pkg-dev
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
