Skip to content
Menu

thisyearnofear

No narrative yet

Is this your project? Claim and verify →

What HEY knows

Building
Shipping consistentlyShipping: 6 meaningful events in 30 days; latest ship yesterday. Evidence Source

Build Momentum 56How it is measured

Latest ship
Code changes this week (since Mon 26 Oct) · 23 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
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-26; HEY first knew on 2026-10-26.
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 thisyearnofear 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 thisyearnofear’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
Shipping.
“Shipping” by the activity rule: 6 meaningful events in the last 30 days, the newest 2026-10-26.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 23 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 7 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 24 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.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 26 Oct) · 23 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 7 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 24 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
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 26 Oct) · 23 commits thisyearnofear/diversify

Code activitySource linked

What changed, in the repository’s own words:

1 active day in thisyearnofear/diversify.

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

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

View evidence ↗ (opens in a new tab)

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

Questions HEY can answer about thisyearnofear — as of 27 Oct

Is thisyearnofear still being built?
DerivedShipping: 6 meaningful events in 30 days; latest ship yesterday. Evidence
What did thisyearnofear ship last?
FactCode changes this week (since Mon 26 Oct) · 23 commits — Code activity, yesterday. Evidence
What does HEY not know about thisyearnofear?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs. Details

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-10-19 – 2026-10-25 · 7 commits thisyearnofear/diversify

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in thisyearnofear/diversify.

    How HEY read this week

    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-10-19 – 2026-10-25 · 7 commits (opens in a new tab)

  2. Code changes, week of 2026-10-19 – 2026-10-25 · 16 commits thisyearnofear/cognivern

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in thisyearnofear/cognivern.

    How HEY read this week

    This week HEY looked inside 1 of 16 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-10-19 – 2026-10-25 · 16 commits (opens in a new tab)

  3. Code changes, week of 2026-10-12 – 2026-10-18 · 24 commits thisyearnofear/diversify

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in thisyearnofear/diversify.

    How HEY read this week

    This week HEY looked inside 1 of 24 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-10-12 – 2026-10-18 · 24 commits (opens in a new tab)

  4. Code changes, week of 2026-10-05 – 2026-10-11 · 35 commits thisyearnofear/diversify

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in thisyearnofear/diversify.

    How HEY read this week

    This week HEY looked inside 3 of 35 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 · 35 commits (opens in a new tab)

  5. Code changes, week of 2026-10-05 – 2026-10-11 · 8 commits thisyearnofear/cognivern

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in thisyearnofear/cognivern.

    How HEY read this week

    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-10-05 – 2026-10-11 · 8 commits (opens in a new tab)

  6. Code changes, week of 2026-09-28 – 2026-10-04 · 66 commits thisyearnofear/diversify

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in thisyearnofear/diversify.

    How HEY read this week

    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. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 66 commits (opens in a new tab)

  7. Code changes, week of 2026-09-21 – 2026-09-27 · 79 commits thisyearnofear/diversify

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in thisyearnofear/diversify.

    How HEY read this week

    This week HEY looked inside 3 of 79 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-21 – 2026-09-27 · 79 commits (opens in a new tab)

  8. Code changes, week of 2026-09-21 – 2026-09-27 · 3 commits thisyearnofear/cognivern

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in thisyearnofear/cognivern.

    How HEY read this week

    This week HEY looked inside 2 of 3 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-21 – 2026-09-27 · 3 commits (opens in a new tab)
Earlier ships (6)

  1. Code changes, week of 2026-09-14 – 2026-09-20 · at least 34 commits thisyearnofear/diversify

    Code activitySource linked

    3 active days in thisyearnofear/diversify.

    How HEY read this week

    This week HEY looked inside 2 of 22 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-14 – 2026-09-20 · at least 34 commits (opens in a new tab)

  2. Code changes, week of 2026-09-14 – 2026-09-20 · at least 4 commits thisyearnofear/cognivern

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in thisyearnofear/cognivern.

    How HEY read this week

    This week HEY looked inside 1 of 4 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-14 – 2026-09-20 · at least 4 commits (opens in a new tab)

  3. Code changes, week of 2026-09-07 – 2026-09-13 · at least 19 commits thisyearnofear/diversify

    Code activitySource linked

    What changed, in the repository’s own words:

    8 active days in thisyearnofear/diversify.

    How HEY read this week

    This week HEY looked inside 1 of 19 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 19 commits (opens in a new tab)

  4. Code changes, week of 2026-09-07 – 2026-09-13 · at least 21 commits thisyearnofear/cognivern

    Code activitySource linked

    What changed, in the repository’s own words:

    14 active days in thisyearnofear/cognivern.

    How HEY read this week

    This week HEY looked inside 1 of 21 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 1 automated commit (bot accounts or a repeating scripted message) not counted.

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

  5. Code changes, week of 2026-08-31 – 2026-09-06 · at least 93 commits thisyearnofear/diversify

    Code activitySource linked

    What changed, in the repository’s own words:

    9 active days in thisyearnofear/diversify.

    How HEY read this week

    This week HEY looked inside 3 of 93 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. 2 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 93 commits (opens in a new tab)

  6. Code changes, week of 2026-08-31 – 2026-09-06 · at least 13 commits thisyearnofear/cognivern

    Code activitySource linked

    What changed, in the repository’s own words:

    13 active days in thisyearnofear/cognivern.

    How HEY read this week

    This week HEY looked inside 2 of 13 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-08-31 – 2026-09-06 · at least 13 commits (opens in a new tab)

What changed

16 changes on HEY’s record for thisyearnofear: 1 build pace change · 15 weeks of code pushed.

All 16 changes for thisyearnofear →

Research coverage

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

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 54d ago.

Building

  • Building activityMeasuredRead 42m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • 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 3d ago.

Code and packages

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