What did vibekit ship last?

Code changes, week of 2026-10-05 – 2026-10-11 · 17 commits — Code activity, 14 days ago.

What does HEY not know about vibekit?

3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs.

vibekit

AI Agents

HEY verified shipping evidence from the project’s own public sources; ownership of this page is not claimed yet.

Is this your project? Claim and verify →

Build on vibe/vibe with any AI: context pack, hosted MCP, one-file templates, recipes. Robinhood Chain testnet.

What HEY knows

Building

Last shipped 14 days agoActive: 1 meaningful event in 30 days; latest ship 14 days ago. Evidence Source

Build Momentum 22How it is measured

Latest ship

Code changes, week of 2026-10-05 – 2026-10-11 · 17 commits · 14d ago · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

This change

Code changes, read from the team’s GitHub · not a deployment

What it names: 1 of 1 commit HEY read changed code. A week of code names no capability.
Stage: Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by: Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment: Not a release or a deployment: code is not a deployment.
Activity: No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When: The source dates it to the week of 2026-10-10; HEY first knew on 2026-10-24.
Not known: No source HEY holds names what this change does.
HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

FollowCreate alert Terminal previewView latest ship

Follow puts vibekit on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me vibekit’s changes

Or read its RSS feed.

Token market · context: No token tracked
Not yet known: Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs.
HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API

What HEY checked — why it says this

Active.: “Active” by the activity rule: 1 meaningful event in the last 30 days, the newest 2026-10-10.; SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.Read3h agoRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 17 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.: The quality gate found verified building evidence from the project's own sources.; Source4 registered sources, 1 of them context only.Read4h agoRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 17 commits source:3e2c71cd-079c-4115-9d30-defad98a135f source:8319b7b1-1248-495c-b116-b78b1f6e2a3bWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.; Market figures are context only and never change activity status. Methodology

LinksWebsite GitHub X Sources

Latest ship

Checked 4h ago

Code changes, week of 2026-10-05 – 2026-10-11 · 17 commits

14d ago

Code activitySource linked

What changed, in the repository’s own words:

3 active days in 0xbadsign/vibekit.

This week HEY looked inside 1 of 17 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:7ddc66b3… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Shared change · Published

vibekit was published on HEY with its sources recorded.

Builder status: Active.

Observed by HEY on 2026-10-24Source: HEY’s research record

Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 10 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about vibekit — as of 2026-10-24

Is vibekit still being built?: DerivedActive: 1 meaningful event in 30 days; latest ship 14 days ago. Evidence
What did vibekit ship last?: FactCode changes, week of 2026-10-05 – 2026-10-11 · 17 commits — Code activity, 14 days ago. Evidence
What does HEY not know about vibekit?: Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs. Details

Recorded, not counted (1)

HEY keeps these on record as context. None counts toward the activity status or Build Momentum; each says why.

Code activityCode changes, week of 2026-10-05 – 2026-10-112026-10-06Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about vibekit? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

3 changes on HEY’s record for vibekit: 1 verification change · 1 new project on HEY · 1 week of code pushed.

Verification3h ago
Research standing moved from Published to Verified builder
See the change
New on HEY4h ago
Project page published
See the change
Code pushed14d ago · recorded by HEY 4h ago
Code changes, week of 2026-10-05 – 2026-10-11 · 17 commits
See the change Source ↗

vibekit on What changed →

The full change record holds 1 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

IdentityMeasuredRead 4h ago.

Building

Building activityMeasuredRead 4h ago.
RepositoriesMeasured
ReleasesMeasured
TimelineMeasured

Official site

Official docsNo sourceHEY read its website and found no link to docs.
API descriptionNot enough yetHEY has not read its website’s published files yet.
Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

Repository detailsMeasuredRead 4h ago.
Published packagesMeasuredRead 4h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources

Website
https://vibercheck.xyz/buildUnverified
Repository
https://github.com/0xBadSign/vibekitOfficial
Repository
https://github.com/0xBadSign/viberquestContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).
X
https://x.com/0xhaileyyOfficial

Build Momentum

Last shipped 14 days ago · Build Momentum 22

SHIPPING: 5
CONSISTENCY: 17
SIGNIFICANCE: 11
EVIDENCE: 70 — strongest component
SOURCES: 67

How steadily, how recently and how verifiably this project ships, from 0 to 100 — this project on its own, never price. How it is measured

Shipping weeks / last 12

Builder Radar

#365 on today’s Builder Radar

The board that ranks builders against each other on verified development, on-chain use and research standing. Price never counts.

The three parts

Development: 22
On-chain use: Not measured: no contract
Research standing: 100
Overall: 29

Methodology

Public code activity

15/ 100

A reading of the public repositories over 60 days — active days, releases, contributors and how recent — kept apart from Build Momentum.

Days with recorded activity: 3 / 60
Contributors: 1
GitHub releases: 0
Last code update: 14d ago

Observed development days. Commit volume is capped and never ranked.

Merged pull requests not measured; the remaining dimensions are reweighted rather than counted as zero.

Is this your project?

Claim the profile to post what you ship and keep this page accurate.

Claiming verifies ownership; by itself it changes no status, score or order.

Claim this project

Builders: show this status. Your HEY badge — Show it on your site or README; it changes no status, score or order.

For the builders: share this research profile — a post, the README badge, an embed and the evidence links.

Something wrong here? Report an error on this page

How HEY researches your project

Your HEY research profile is liveFor the team behind vibekit: share it, badge it, embed it.

HEY verified vibekit as a builder: an official source with a meaningful ship, and evidence on Robinhood Chain. This page updates itself as you ship.

Open the full share pack

Share verified builder status

Post on X Share card image

vibekit — Active · Verified Builder · latest ship 10 Oct: Code changes, week of 2026-10-05 – 2026-10-11 · 17 commits · on HEY Research Lab
https://heyresearch.xyz/project/0xbadsign-vibekit

Add HEY badge to GitHub

Paste into your README. It shows your activity status and last ship, and links here.

[![vibekit on HEY Research Lab](https://heyresearch.xyz/api/badge/0xbadsign-vibekit)](https://heyresearch.xyz/project/0xbadsign-vibekit?utm_source=badge&utm_medium=readme)

Add HEY intelligence to your site

A live builder widget, the same facts as this page. Choose a variant and theme.

<script src="https://heyresearch.xyz/embed/hey-project.js" async></script>
<hey-project project="0xbadsign-vibekit" variant="builder" theme="auto">
  <a href="https://heyresearch.xyz/project/0xbadsign-vibekit">vibekit on HEY Research Lab</a>
</hey-project>

Canonical page: https://heyresearch.xyz/project/0xbadsign-vibekit
API: https://heyresearch.xyz/api/projects/0xbadsign-vibekit/snapshot
Changes feed: https://heyresearch.xyz/api/changes?project=0xbadsign-vibekit
Research receipts: An agent citing this project names it as { "subjectType": "project", "subject": { "chainId": 4663, "projectSlug": "0xbadsign-vibekit" } }. How receipts work

Everything here is public. HEY never contacts builders about it.

Embeddable badgeMethodology