Skip to content
Menu

milesdev888

No narrative yet

Is this your project? Claim and verify →

Guardian Multichain Scan v2 — paste-first scanner for Solana, Ethereum, Base, Arbitrum, and Robinhood Chain. Grades and patterns, not verdicts.

What HEY knows

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

Build Momentum 32How it is measured

Latest ship
Scanner Step 2 390px screenshots (review assets) · · GitHub release

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

Latest change
Derived17 days ago: 3 meaningful ships in the 7 days to 5 Oct, 0 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-10-05; HEY first knew on 2026-10-05.
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 milesdev888 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 milesdev888’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
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

HEY can answer 8 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: 3 meaningful events in the last 30 days, the newest 2026-10-05.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsScanner Step 2 390px screenshots (review assets)Code changes, week of 2026-10-05 – 2026-10-11 · 1 commitCode changes, week of 2026-09-28 – 2026-10-04 · 5 commits+2 moreWhat 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.ReadRecordsScanner Step 2 390px screenshots (review assets)Code changes, week of 2026-10-05 – 2026-10-11 · 1 commitCode changes, week of 2026-09-28 – 2026-10-04 · 5 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
LinksWebsiteGitHubSources

Latest ship

Checked

Scanner Step 2 390px screenshots (review assets)milesdev888/cyre-scan

GitHub releaseSource linked

Review-only 390px before/after shots. Not part of the app tree.

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

View evidence ↗Post this ship on X

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 milesdev888 — as of 2026-10-22

Is milesdev888 still being built?
DerivedActive: 3 meaningful events in 30 days; latest ship 17 days ago. Evidence
What did milesdev888 ship last?
FactScanner Step 2 390px screenshots (review assets) — GitHub release, 17 days ago. Evidence
What does HEY not know about milesdev888?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs. Details

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 1 commitmilesdev888/cyre-scan

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in milesdev888/cyre-scan.

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

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

  2. Code changes, week of 2026-09-28 – 2026-10-04 · 5 commitsmilesdev888/cyre-scan

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in milesdev888/cyre-scan.

    This week HEY looked inside 2 of 5 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-28 – 2026-10-04 · 5 commits (opens in a new tab)

  3. Code changes, week of 2026-09-07 – 2026-09-13 · 64 commitsmilesdev888/guardian-scan

    Code activitySource linked

    4 active days in milesdev888/guardian-scan.

    A burst of 64 commits this week; HEY is looking inside a sample before it says what changed. So far, HEY looked inside 16 of 64 commits to see what changed: 1 changed code, 15 could not be classified.

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

  4. Code changes, week of 2026-08-31 – 2026-09-06 · at least 22 commitsmilesdev888/guardian-scan

    Code activitySource linked

    2 active days in milesdev888/guardian-scan.

    HEY could not tell what 22 commits changed this week. This week HEY looked inside 22 commits to see what changed: 22 could not be classified.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 22 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 milesdev888? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

6 changes on HEY’s record for milesdev888: 1 release · 1 build pace change · 4 weeks of code pushed.

All 6 changes for milesdev888 →

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 8 of the 10 research questions that apply.

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 6h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 17d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 5d ago.

Code and packages

  • Repository detailsMeasuredRead 11h ago.
  • Published packagesMeasuredRead 11h 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