Text To Cad
A library of agent skills for CAD, CAE and CAM
Is Text To Cad safe? Promising trust profile, but some evidence still deserves review.
Compare Text To Cad
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Text To Cad scores 60.3/100 (Grade C), ranked #99 of 351 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 4.5/10; 36% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Text To Cad compares in Agent Skills
- #97 Cc Skills Golang 60.4 +0.1
- #98 Dotnet Skills 60.4 +0.1
- #99 Text To Cad 60.3 this agent
- #100 drawio-skill 60.3 ±0
- #101 I Have Adhd 60.2 −0.1
Bars show each HVTrust score; the tick marks Text To Cad’s 60.3.
Where the 60.3 comes from
HVTrust dimensions vs the Agent Skills average
60.3 / 100 · 100.0% confidenceText To Cad Agent Skills average (351 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
90.3 / 100Supply Chain Trust
Common questions about Text To Cad
Does Text To Cad publish package provenance?
Does Text To Cad have an OpenSSF Scorecard?
Is Text To Cad actively maintained?
What license does Text To Cad use?
Are Text To Cad'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 Text To Cad'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 Text To Cad?
For maintainers
HVTrust scores Text To Cad 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/text-to-cad)
<a href="https://hvtracker.net/agents/text-to-cad"><img src="https://hvtracker.net/badge/text-to-cad.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.3 · Raw JSON