Dyad has an HVTrust score of 60.9/100 (Grade C), ranked #208 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Dyad?

Dyad scores 60.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 21.1k GitHub stars and is categorized under UI & App Builders.

Dyad

dyad-sh/dyad

Local, open-source AI app builder for power users ✨ v0 / Lovable / Replit / Bolt alternative 🌟 Star if you like it!

UI & App Builders TypeScript Grade C Listed NOASSERTION

60.9/100

Rank #208 of 468

Compare Dyad

How does it stack up against its UI & App Builders neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-06 · 0d ago

Recent change

No recent signal change

Is Dyad safe? Dyad scores 60.9/100 (Grade C), ranked #208 of 468 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 3.7/10; 100% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

#6 Cherry Studio — 64.4 (C) → #7 Odysseus — 63.0 (C) → #9 ToolJet — 60.5 (C) → #10 Eigent — 57.8 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-07-22

Rank Moved

Rank rose 11 spots (#206 → #195)

2026-07-15

Rank Moved

Rank dropped 10 spots (#197 → #207)

2026-07-13

Rank Moved

Rank dropped 24 spots (#165 → #189)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.7/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with OpenUI Get email alerts for Dyad View UI & App Builders Report missing data

91.8

Activity sub-score · out of 100

In UI & App Builders

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

2026-07-05 2026-08-06

Activity & Reach

Stars

21.1k

Forks

2.6k

Last Push

2026-08-06

today

Commits (4 wk)

280

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

264

Rank Change

▲2

was #210

Analysis

HVTrust Dimensions vs UI & App Builders

60.9 / 100 · 100.0% confidence

Dyad UI & App Builders average (15 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

9.6 / 25

1.8 below avg 11.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.9 below avg 12.7

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

0.7 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

3.0 above avg 17.0

AdoptionLog-scaled stars · package downloads

10.4 / 20

2.6 below avg 13.0

Activity Inputs

91.8 / 100

StarsRepository reach

25.9 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Aug 5, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 6

Contributors 3

Dangerous-Workflow 0

Dependency-Update-Tool 0

Fuzzing 0

License 9

Maintained 10

Packaging -1

Pinned-Dependencies 3

SAST 4

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Dyad safe?

Dyad has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Dyad publish package provenance?

No published build provenance is currently detected for Dyad. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Dyad have an OpenSSF Scorecard?

Dyad has an OpenSSF Scorecard score of 3.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Dyad actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Dyad use?

Dyad ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Dyad's commits signed?

100% of the last 100 commits to Dyad are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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.

Compare Dyad head-to-head

Dyad vs OpenUI → Dyad vs Neo → Dyad vs Tambo →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

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 Server Support

high confidence

Implemented

Dyad appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

5 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

5 tags

Broad capability areas detected.

browser
code
database
filesystem
shell

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Dyad?

For maintainers

HVTrust scores Dyad 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-07-22

Rank Moved

Rank rose 11 spots (#206 → #195)

2026-07-15

Rank Moved

Rank dropped 10 spots (#197 → #207)

2026-07-13

Rank Moved

Rank dropped 24 spots (#165 → #189)

2026-06-24

Scorecard Added

OSSF Scorecard: 3.4/10

2026-06-24

Grade Changed

Trust grade D → C

2026-06-24

Rank Moved

Rank rose 118 spots (#277 → #159)

2026-06-24

HVTrust Changed

HVTrust up 34.5pts (27.3 → 61.8)

2026-06-23

Rank Moved

Rank dropped 23 spots (#254 → #277)

2026-06-22

Rank Moved

Rank dropped 10 spots (#244 → #254)

2026-06-21

Rank Moved

Rank dropped 16 spots (#228 → #244)

2026-06-20

Newly Listed

First tracked at rank #228

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/dyad.svg)](https://hvtracker.net/agents/dyad)
            
HTML:
            <a href="https://hvtracker.net/agents/dyad"><img src="https://hvtracker.net/badge/dyad.svg" alt="HVTrust"></a>

Other agents in UI & App Builders

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON