DSH Web UI
DeepSeek Harness (DSH) Web 插件聚合生态 · 万物皆插件,通过创意工坊分发||DeepSeek Harness (DSH) Web Plugin Aggregation Ecosystem · Everything is a plugin, distributed via the Creative Workshop
Is DSH Web UI safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare DSH Web UI
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: DSH Web UI scores 54.6/100 (Grade C), ranked #193 of 396 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.8/10; 2% of recent commits are signed; last pushed 2026-11-17. Every point is earned from checkable signals — never paid placement. How scoring works →
How DSH Web UI could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 2.8 to 9.0lowest checks: Binary-Artifacts 0, CII-Best-Practices 0, Code-Review 0 +12.9 → 67.5 B · #49 of 396
- Sign every commit2% signed today +4.9 → 59.5 C · #125 of 396
Chain of custody
Scanners check what the code says. This traces who ships DSH Web UI and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.
-
Source Partly signed
github.com/zhu1090093659/dsh-web, Apache-2.0, last pushed 2026-11-17. 2% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 2.8/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection4
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 0Branch-Protection 4CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 0Packaging -1Pinned-Dependencies 0SAST 10Security-Policy 0Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. DSH Web UI is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-08-30 OSSF Scorecard: 3.6/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues DSH Web UI’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.
How DSH Web UI compares in Agent Skills
- #191 Spring Boot Skills 54.6 ±0
- #192 SwiftUI Agent Skill 54.6 ±0
- #193 DSH Web UI 54.6 this agent
- #194 rea-video 54.6 ±0
- #195 VEED OpenEdit 54.5 −0.1
Bars show each HVTrust score; the tick marks DSH Web UI’s 54.6.
Where the 54.6 comes from
HVTrust dimensions vs the Agent Skills average
54.6 / 100 · 100.0% confidenceDSH Web UI Agent Skills average (396 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
87.1 / 100Common questions about DSH Web UI
Does DSH Web UI publish package provenance?
Does DSH Web UI have an OpenSSF Scorecard?
Is DSH Web UI actively maintained?
What license does DSH Web UI use?
Are DSH Web UI's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to DSH Web UI's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain DSH Web UI?
For maintainers
HVTrust scores DSH Web UI from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/dsh-web-ui)
<a href="https://hvtracker.net/agents/dsh-web-ui"><img src="https://hvtracker.net/badge/dsh-web-ui.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON