Skip to content
Menu

Gitlawb

Launchpad

Is this your project? Claim and verify →

On-chain contracts for the Gitlawb protocol

What HEY knows

Building
Last shipped yesterdayShipping: 3 meaningful events in 30 days; latest ship yesterday. Evidence Source

Build Momentum 40How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · 66 commits · · Code activity

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

This change
Code changes, read from the team’s GitHub · not a deployment
What it names
3 of 3 commits 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-18; HEY first knew on 2026-10-12.
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 alertTerminal previewView latest ship
Share

Follow puts Gitlawb 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 Gitlawb’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

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
Shipping.
“Shipping” by the activity rule: 3 meaningful events in the last 30 days, the newest 2026-10-18.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 66 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 75 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 12 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 66 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 75 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 12 commits+5 moreWhat 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
LinksGitHubSources

Latest ship

Checked

Code changes, week of 2026-10-12 – 2026-10-18 · 66 commitstwigpine/openlaunch

Code activitySource linked

What changed, in the repository’s own words:

6 active days in twigpine/openlaunch.

This week HEY looked inside 3 of 66 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

View evidence ↗

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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Gitlawb — as of 2026-10-19

Is Gitlawb still being built?
DerivedShipping: 3 meaningful events in 30 days; latest ship yesterday. Evidence
What did Gitlawb ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 66 commits — Code activity, yesterday. Evidence
What does HEY not know about Gitlawb?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 75 commitstwigpine/openlaunch

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in twigpine/openlaunch.

    This week HEY looked inside 3 of 75 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 75 commits (opens in a new tab)

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 12 commitsgitlawb/openlaunch

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in gitlawb/openlaunch.

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

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 12 commits (opens in a new tab)

  3. Code changes, week of 2026-09-21 – 2026-09-27 · 12 commitstwigpine/openlaunch

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in twigpine/openlaunch.

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

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 12 commits (opens in a new tab)

  4. Code changes, week of 2026-09-14 – 2026-09-20 · at least 58 commitsgitlawb/openlaunch

    Code activitySource linked

    What changed, in the repository’s own words:

    4 active days in gitlawb/openlaunch.

    This week HEY looked inside 3 of 58 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 58 commits (opens in a new tab)

  5. Code changes, week of 2026-09-07 – 2026-09-13 · at least 5 commitsgitlawb/openlaunch

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in Gitlawb/openlaunch.

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

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 5 commits (opens in a new tab)

  6. Code changes, week of 2026-07-13 – 2026-07-19 · at least 1 commitgitlawb/contracts

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in Gitlawb/contracts.

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes, week of 2026-07-13 – 2026-07-19 · at least 1 commit (opens in a new tab)

  7. Code changes, week of 2026-07-13 – 2026-07-19 · at least 1 committwigpine/contracts

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in twigpine/contracts.

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes, week of 2026-07-13 – 2026-07-19 · at least 1 commit (opens in a new tab)

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 Gitlawb? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

8 changes on HEY’s record for Gitlawb: 8 weeks of code pushed.

All 8 changes for Gitlawb →

The full change record holds 4 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 1mo ago.

Building

  • Building activityMeasuredRead 15m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesMeasuredRead 6d 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