vibesdk

An open-source vibe coding platform that helps you build your own vibe-coding platform, built entirely on Cloudflare sta

UI & App Builders TypeScript Grade C Listed MIT
54.5/100
Rank #792 of 1328
Compare vibesdk

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-08 · 12d ago
Recent change
Rank +4

Is vibesdk safe? vibesdk scores 54.5/100 (Grade C), ranked #792 of 1328 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 5.2/10; 36% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-19
Rank Moved
Rank dropped 16 spots (#775 → #791)
2026-09-18
Rank Moved
Rank dropped 19 spots (#756 → #775)
2026-09-17
Rank Moved
Rank dropped 17 spots (#739 → #756)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
70.6
Activity sub-score · out of 100
#13

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 →

Signals refreshed 2026-09-20 18:03 UTC · Repo last pushed 12 days ago

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
5.4k
Forks
1.3k
Last Push
2026-09-08
12 days ago
Commits (4 wk)
6
Downloads (7d)
HN mentions (30d)
Open Issues
10
Rank Change
▼1
was #791

Analysis

HVTrust Dimensions vs UI & App Builders

54.5 / 100 · 100.0% confidence

vibesdk UI & App Builders average (17 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.3 / 25
3.3 below avg 11.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.1 below avg 12.9
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
0.5 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
14.6 / 20
in line with avg 15.0
AdoptionLog-scaled stars · package downloads
9.0 / 20
3.5 below avg 12.5

Activity Inputs

70.6 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
23.3 / 25
ActivityRecent commits
10.5 / 25
CommunityFork signal
14.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.2 / 10
OpenSSF Scorecard · scanned Sep 19, 2026
Signed Commits
36%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 1
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 5
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is vibesdk safe?

Public trust evidence for vibesdk is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does vibesdk publish package provenance?
No published build provenance is currently detected for vibesdk. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does vibesdk have an OpenSSF Scorecard?
vibesdk has an OpenSSF Scorecard score of 5.2/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 vibesdk actively maintained?
Maintained. Last push was 12 days ago.
What license does vibesdk use?
vibesdk ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are vibesdk's commits signed?
36% of the last 100 commits to vibesdk 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.

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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
2 tags
Broad capability areas detected.
  • browser
  • code
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 vibesdk?

For maintainers

HVTrust scores vibesdk 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
Rank 26Listed 1Score 1HVTrust 1Grade 1Scorecard 1
2026-09-19
Rank Moved
Rank dropped 16 spots (#775 → #791)
2026-09-18
Rank Moved
Rank dropped 19 spots (#756 → #775)
2026-09-17
Rank Moved
Rank dropped 17 spots (#739 → #756)
2026-09-14
Rank Moved
Rank dropped 12 spots (#720 → #732)
2026-09-13
Rank Moved
Rank dropped 28 spots (#692 → #720)
2026-09-12
Rank Moved
Rank dropped 15 spots (#677 → #692)
2026-09-11
Rank Moved
Rank dropped 15 spots (#662 → #677)
2026-09-09
Rank Moved
Rank dropped 26 spots (#629 → #655)
2026-09-07
Rank Moved
Rank dropped 30 spots (#590 → #620)
2026-09-06
Rank Moved
Rank dropped 11 spots (#579 → #590)
2026-09-05
Rank Moved
Rank dropped 74 spots (#505 → #579)
2026-09-04
Rank Moved
Rank dropped 25 spots (#480 → #505)
2026-09-03
Rank Moved
Rank dropped 21 spots (#459 → #480)
2026-09-01
Scorecard Added
OSSF Scorecard: 5.3/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 722 spots (#1183 → #461)
2026-09-01
HVTrust Changed
HVTrust up 35.7pts (22.5 → 58.2)
2026-08-31
Rank Moved
Rank dropped 17 spots (#1166 → #1183)
2026-08-30
Rank Moved
Rank dropped 36 spots (#1130 → #1166)
2026-08-29
Rank Moved
Rank dropped 54 spots (#1076 → #1130)
2026-08-28
Rank Moved
Rank dropped 33 spots (#1043 → #1076)
2026-08-27
Rank Moved
Rank dropped 24 spots (#1019 → #1043)
2026-08-26
Rank Moved
Rank dropped 93 spots (#926 → #1019)
2026-08-24
Rank Moved
Rank dropped 10 spots (#920 → #930)
2026-08-17
Rank Moved
Rank rose 11 spots (#940 → #929)
2026-08-16
Rank Moved
Rank dropped 22 spots (#918 → #940)
2026-08-12
Rank Moved
Rank rose 13 spots (#925 → #912)
2026-08-10
Rank Moved
Rank rose 35 spots (#957 → #922)
2026-08-10
Activity Score Changed
Activity score up 13pts (74 → 87)
2026-08-08
Rank Moved
Rank dropped 468 spots (#480 → #948)
2026-08-06
Newly Listed
First tracked at rank #489

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/vibesdk.svg)](https://hvtracker.net/agents/vibesdk)
HTML:
<a href="https://hvtracker.net/agents/vibesdk"><img src="https://hvtracker.net/badge/vibesdk.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.3 · Raw JSON