Skip to content
Menu

Og Scan

Uncategorised

Is this your project? Claim and verify →

Built by @audifyx

What HEY knows

Building
Shipping consistentlyShipping: 5 meaningful events in 30 days; latest ship 3 days ago. Evidence Source

Build Momentum 52How it is measured

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

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

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Og Scan 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 Og Scan’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
Shipping.
“Shipping” by the activity rule: 5 meaningful events in the last 30 days, the newest 2026-10-16.
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 · 238 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 6 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 249 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.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 238 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 6 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 249 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-10-12 – 2026-10-18 · 238 commits

Code activitySource linked

What changed, in the repository’s own words:

5 active days in audifyx/og-scan.

This week HEY looked inside 5 of 238 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

Record ship:2e9c3865… · 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 Og Scan — as of 2026-10-19

Is Og Scan still being built?
DerivedShipping: 5 meaningful events in 30 days; latest ship 3 days ago. Evidence
What did Og Scan ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 238 commits — Code activity, 3 days ago. Evidence
What does HEY not know about Og Scan?
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-10-05 – 2026-10-11 · 6 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in audifyx/og-scan.

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

    View evidence

  2. Code changes, week of 2026-09-28 – 2026-10-04 · 249 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in audifyx/og-scan.

    This week HEY looked inside 3 of 249 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

  3. Code changes, week of 2026-09-21 – 2026-09-27 · at least 100 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    at least 5 active days in audifyx/og-scan since 2026-09-23; the count stops at the newest 100 commits listed.

    This week HEY looked inside 3 of 100 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

  4. Code changes, week of 2026-09-14 – 2026-09-20 · at least 68 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in audifyx/og-scan.

    This week HEY looked inside 3 of 68 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

  5. Code changes, week of 2026-09-07 – 2026-09-13 · at least 53 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in audifyx/og-scan.

    This week HEY looked inside 3 of 53 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

  6. Code changes, week of 2026-08-31 – 2026-09-06 · at least 47 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    9 active days in audifyx/og-scan.

    This week HEY looked inside 3 of 47 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

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

What changed

7 changes on HEY’s record for Og Scan: 7 weeks of code pushed.

All 7 changes for Og Scan →

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 8m 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 13h ago.
  • Published packagesMeasuredRead 13h 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