Skip to content
Menu

eliaskosho

No narrative yet

Is this your project? Claim and verify →

Delivery Guy ($DELIVERY) on Robinhood Chain. Static site: HTML, CSS, vanilla JS.

What HEY knows

Building
Last shipped 37 days agoActive: 0 meaningful events in 30 days; latest ship 37 days ago. Evidence Source

Build Momentum 16How it is measured

Latest ship
Code changes, week of 2026-09-14 – 2026-09-20 · 2 commits · · Code activity

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

Latest change
Derived33 days ago: 3 meaningful ships in the 7 days to 18 Sep, 1 the 7 days before. Evidence

HEY’s own reading

What this change is
What it names
HEY’s own reading names no capability.
Stage
HEY’s own reading of the record, not something the project shipped.
Reported by
HEY’s reading of the record. HEY’s own reading of the record: nothing to corroborate.
Release and deployment
Not a release or 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 2026-09-18; HEY first knew on 2026-09-18. HEY indexed it later, as history.
Not known
  • No source HEY holds names what this change does.

Evidence: signal 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 eliaskosho 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 eliaskosho’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 (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer.

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's longer window: 2 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-14, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 2 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 7 commitsCode changes, week of 2026-08-31 – 2026-09-06 · at least 8 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, 0 of them context only.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 2 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 7 commitsCode changes, week of 2026-08-31 – 2026-09-06 · at least 8 commits+3 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
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-09-14 – 2026-09-20 · 2 commitseliaskosho/habibi

Code activitySource linked

What changed, in the repository’s own words:

1 active day in eliaskosho/habibi.

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

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

View evidence ↗

Shared change · Development spike

eliaskosho: 3 meaningful ships were recorded in the latest 7 days, from 1 in the 7 days before.

Builder status: Active.

Dated 2026-09-18 by the sourceSource: HEY Signal

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

Questions HEY can answer about eliaskosho — as of 2026-10-21

Is eliaskosho still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 37 days ago. Evidence
What did eliaskosho ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · 2 commits — Code activity, 37 days ago. Evidence
What does HEY not know about eliaskosho?
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer. Details

Build timeline

  1. Code changes, week of 2026-09-07 – 2026-09-13 · at least 7 commitseliaskosho/habibi

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in eliaskosho/habibi.

    This week HEY looked inside 2 of 7 commits to see what changed: 1 changed code, 1 documentation or maintenance only. 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 7 commits (opens in a new tab)

  2. Code changes, week of 2026-09-07 – 2026-09-13 · 5 commitseliaskosho/delivery-guy

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in eliaskosho/delivery-guy.

    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 · 5 commits (opens in a new tab)

  3. Code changes, week of 2026-08-31 – 2026-09-06 · at least 8 commitseliaskosho/delivery-guy

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in eliaskosho/delivery-guy.

    This week HEY looked inside 1 of 8 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-08-31 – 2026-09-06 · at least 8 commits (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 eliaskosho? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

5 changes on HEY’s record for eliaskosho: 1 build pace change · 4 weeks of code pushed.

eliaskosho on What changed →

The full change record holds 2 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 12h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsSource unavailableIts website did not answer.
  • API descriptionSource unavailableIts website did not answer.
  • Official site changesSource unavailableIts website did not answer.

Code and packages

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