Diagram Design
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Factory Droid, and Pi. 44 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Is Diagram Design safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Diagram Design
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Diagram Design scores 26.1/100 (Grade D), ranked #359 of 371 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 45% of recent commits are signed; last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →
How Diagram Design 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 to 9.0no OSSF Scorecard result yet +45.2 → 71.3 B · #29 of 371
- Sign every commit45% signed today +1.4 → 27.5 D · #359 of 371
Chain of custody
Scanners check what the code says. This traces who ships Diagram Design 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/cathrynlavery/diagram-design, MIT, last pushed 2026-10-10. 45% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages None
No registry package. Diagram Design is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Diagram Design.
Evidence behind this score
Coverage D: 1 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Diagram Design’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 Diagram Design compares in Agent Skills
- #357 Universal Modder 27.9 +1.8
- #358 Adversarial Spec 27.8 +1.7
- #359 Diagram Design 26.1 this agent
- #360 Clawhub 25.6 −0.5
- #361 brag 23.0 −3.1
Bars show each HVTrust score; the tick marks Diagram Design’s 26.1.
Where the 26.1 comes from
HVTrust dimensions vs the Agent Skills average
26.1 / 100 · 50.0% confidenceDiagram Design Agent Skills average (371 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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
94.3 / 100Common questions about Diagram Design
Does Diagram Design publish package provenance?
Does Diagram Design have an OpenSSF Scorecard?
Is Diagram Design actively maintained?
What license does Diagram Design use?
Are Diagram Design'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
Maintain Diagram Design?
For maintainers
HVTrust scores Diagram Design 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/diagram-design)
<a href="https://hvtracker.net/agents/diagram-design"><img src="https://hvtracker.net/badge/diagram-design.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON