Skip to content
Menu

Tempo

No narrative yet

Is this your project? Claim and verify →

What HEY knows

Building
Quiet for 56 daysQuiet: 0 meaningful events in 30 days; latest ship on 2026-08-26. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-08-24 – 2026-08-30 · 8 commits · · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

Latest change
Derived20 days ago: Code changes, week of 2026-09-28 – 2026-10-04. Not counted as building. Evidence Source

Maintenance only, read from the team’s GitHub · not a new capability

What this change is
What it names
Maintenance only, not a new capability: 0 of 0 commits HEY read were documentation, dependency or maintenance changes, and none changed code.
Stage
Maintenance is not a new capability, and code is not a deployment.
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-01; HEY first knew on 2026-09-29.
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 Tempo 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 Tempo’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
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-08-26.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-08-24 – 2026-08-30 · 8 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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.
Source1 registered source, 0 of them context only.ReadRecordsCode changes, week of 2026-08-24 – 2026-08-30 · 8 commitssource:27622743-75d5-42e1-a457-fa603e2051ffWhat 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-08-24 – 2026-08-30 · 8 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in dcftradingcrypt/tempo.

HEY could not tell what 5 commits changed this week. This week HEY looked inside 8 commits to see what changed: 3 documentation or maintenance only, 5 could not be classified. 7 automated commits (bot accounts or a repeating scripted message) not counted.

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

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

Is Tempo still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship on 2026-08-26. Evidence
What did Tempo ship last?
FactCode changes, week of 2026-08-24 – 2026-08-30 · 8 commits — Code activity, on 2026-08-26. Evidence
What does HEY not know about Tempo?
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-09-28 – 2026-10-04 · 4 commits

    Code activitySource linked

    4 active days in dcftradingcrypt/tempo.

    Automated commits only — not counted as building. 7 automated commits (bot accounts or a repeating scripted message) not counted.

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

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 7 commits

    Code activitySource linked

    7 active days in dcftradingcrypt/tempo.

    Automated commits only — not counted as building. 7 automated commits (bot accounts or a repeating scripted message) not counted.

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

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

    Code activitySource linked

    7 active days in dcftradingcrypt/tempo.

    Automated commits only — not counted as building. 7 automated commits (bot accounts or a repeating scripted message) not counted.

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

  4. Code changes, week of 2026-09-07 – 2026-09-13

    Code activitySource linked

    88 active days in dcftradingcrypt/Tempo.

    Automated commits only — not counted as building. 7 automated commits (bot accounts or a repeating scripted message) not counted.

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

  5. Code changes, week of 2026-08-31 – 2026-09-06

    Code activitySource linked

    89 active days in dcftradingcrypt/Tempo.

    Automated commits only — not counted as building. 7 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 (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 Tempo? 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 Tempo: 6 weeks of code pushed.

All 6 changes for Tempo →

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 16h 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 3d ago.
  • Published packagesMeasuredRead 3d 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