updated 2026-08-19 05:02 UTC

vibesdk

cloudflare/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 D Listed MIT
23.0/100
Rank #936 of 1308
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 D · 1/5 signals
Last push
2026-08-18 · 1d ago
Recent change
Rank +2

Is vibesdk safe? vibesdk scores 23.0/100 (Grade D), ranked #936 of 1308 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; 42% of recent commits are signed; last pushed 2026-08-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

#13 Srcbook — 50.2 (C) → #14 Convex Chef — 48.4 (D) → #15 Bolt — 34.9 (D) → #17 tinykit — 11.6 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
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)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
Compare with another agent Get email alerts for vibesdk View UI & App Builders Report missing data
86.8
Activity sub-score · out of 100
#16
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 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 →

Signals refreshed 2026-08-19 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
5.3k
Forks
1.2k
Last Push
2026-08-18
yesterday
Commits (4 wk)
173
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
9
Rank Change
▼5
was #931

Analysis

HVTrust Dimensions vs UI & App Builders

23.0 / 100 · 50.0% confidence

vibesdk UI & App Builders average (17 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.1 / 25
8.0 below avg 10.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.7 below avg 12.5
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
3.9 above avg 16.0
AdoptionLog-scaled stars · package downloads
8.9 / 20
3.5 below avg 12.4

Activity Inputs

86.8 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
42%
of last 100 commits verified

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?
No OpenSSF Scorecard data is currently published for vibesdk. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is vibesdk actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
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?
42% 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: API keys or service config markers documented.
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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 5Listed 1Score 1
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
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 23.0 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON