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 →
Data as of (UTC)
What it doesAI
Local zero-dependency repo risk scanner and resident guard covering licenses, dependency CVEs, secrets, PII and OWASP code risks with 118 rules.
- 118 explainable rules across license, SBOM/CVE, secrets, PII and OWASP/CWE code risks
- Zero-dependency local static analysis that runs from the CLI with no network or setup
- Gate-friendly verdicts and drift guard so risk findings cannot silently regress
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:mw2wbyys6t-sudo/provemark-open#v0.7.1Install 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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current |
|---|---|
| v0.7.1 | ○ |
v0.7.1github○ 1 ecosystem plugin2026-11-11
https://github.com/mw2wbyys6t-sudo/provemark-open
○dsh 0.2.2-rc.1current2026-11-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/mw2wbyys6t-sudo/provemark-open#v0.7.1
ID: provemark-open@v0.7.1@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-11 · expires: 2026-11-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.
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/provemark-open/?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 low; dynamic medium (authoritative when present) → overall medium.
—v0.7.1git2026-11-11v0.7.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalsecretSk · secrets
mock-repo/src/config.py:1OPENAI_API_KEY = "sk-proj-Q7mZ2pLx9TvR4sKd8WnB3yHf6" - criticalsecretSk · secrets
mock-repo/src/legacy.py:1OPENAI_API_KEY = "sk-proj-Q7mZ2pLx9TvR4sKd8WnB3yHf6"
show 2 audit findings
- mediumcordis.patch.yml uses a !!js tag that evaluates arbitrary JavaScript at config-load time
plugin/provemark-dsh/cordis.patch.yml:48The DSH loader evaluates !!js tags when applying the patch, so this file executes JavaScript inside the host process at plugin load, before any user action. The payload here is benign (resolving the skills dir relative to the profile), but it deliberately reaches Node builtins through process.getBuiltinModule, bypassing normal module-resolution restrictions, and it establishes an eval channel in shipped package data. Anyone able to modify the package or the patch layer (registry tampering, a writable profile patch dir) gains code execution in the harness process without further interaction.
- lowTest-fixture corpus ships credential-like strings and personal data
mock-repo/src/forms.py:4mock-repo/src/*.py (and its config.py OPENAI_API_KEY / SUPPORT_EMAIL / SUPPORT_PHONE, loader.py base64-decoded key) contain hardcoded key-like strings, a Singapore NRIC and card numbers. They appear to be synthetic fixtures for the plugin's own secret scanner (companion file app.py imports 'totally_fake_pkg_xyz'), and are not loaded or executed by the plugin at runtime. Residual risk is low: secret-scanning on the published package will flag them, and if any value were a real key it would be publicly exposed.
Legitimate repo-scanning plugin; main risk is a !!js YAML tag that evaluates arbitrary JavaScript at patch-load time; secret-like values are only test fixtures.
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-11-08 · activity: Active
• Repo created: 2026-11-02
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 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 @mw2wbyys6t-sudo/provemark-open?
@mw2wbyys6t-sudo/provemark-open is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 @mw2wbyys6t-sudo/provemark-open?
Run dsh plugin --profile web add github:mw2wbyys6t-sudo/provemark-open#v0.7.1 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-11-11 (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.