Skip to content
Menu

Nuthatch Org

Data

Is this your project? Claim and verify →

Be your own indexer. One Rust binary, one command, live indexed API in under two minutes. No mandatory third-party data dependency.

What HEY knows

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

Build Momentum 81How it is measured

Latest ship
v5.8.2 · · GitHub release

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

This change
Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “v5.8.2”.
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
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 established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to 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-20 20:25 UTC; HEY first knew on 2026-10-20.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.

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 Nuthatch Org 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 Nuthatch Org’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
Unknown1 gap: API description (not enough yet). HEY has not read its website’s published files yet.

HEY can answer 9 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: 29 meaningful events in the last 30 days, the newest 2026-10-20.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv5.8.2Code changes this week (since Mon 19 Oct) · 117 commitsv5.7.2+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.
Source16 registered sources, 1 of them context only.ReadRecordsv5.8.2Code changes this week (since Mon 19 Oct) · 117 commitsv5.7.2+7 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

v5.8.2nuthatch-org/nuthatch

GitHub releaseSource verified

Nuthatch 5.8.2 keeps a seal-direct backfill on a dense chain inside the per-cursor memory budget. There is no storage migration, and no nest's NID, registry hash or sealed segment changes. Memory on a dense chain Peak RSS of bench backfill --seal-direct over 30,000 blocks… Show all

Nuthatch 5.8.2 keeps a seal-direct backfill on a dense chain inside the per-cursor memory budget. There is no storage migration, and no nest's NID, registry hash or sealed segment changes. Memory on a dense chain Peak RSS of bench backfill --seal-direct over 30,000 blocks, against a local node serving N transactions per block, macOS release build: | | before | after | |---|---|---| | blocks table, 3,000 txs/block, --concurrency 8 | 3,078 to 3,090 MiB | 238 to 245 MiB | | blocks table, 1,000 txs/block, --concurrency 8 | 1,010 to 1,039 MiB | 224 to 245 MiB | | events only, 3,000…

Record ship:e77b358a… · 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.

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

Is Nuthatch Org still being built?
DerivedShipping: 29 meaningful events in 30 days; latest ship yesterday. Evidence
What did Nuthatch Org ship last?
Factv5.8.2 — GitHub release, yesterday. Evidence
What does HEY not know about Nuthatch Org?
Unknown1 gap: API description (not enough yet). HEY has not read its website’s published files yet. Details

Build timeline

  1. Code changes this week (since Mon 19 Oct) · 117 commitsnuthatch-org/nuthatch

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in nuthatch-org/nuthatch.

    This week HEY looked inside 7 of 117 commits to see what changed: 3 changed code, 3 documentation or maintenance only, 1 could not be classified. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes this week (since Mon 19 Oct) · 117 commits (opens in a new tab)

  2. 2 releases in nuthatch-org/nuthatch on 20 Oct

    GitHub release

    Show all 2 releases

    1. v5.8.1nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.8.1 refuses to reopen a store, or reuse its segments, after an event's indexed parameters have moved. There is no storage migration, and no nest's NID or registry hash changes. A swapped indexed parameter is refused, not misread An event's indexed markers decide which… Show all

      Nuthatch 5.8.1 refuses to reopen a store, or reuse its segments, after an event's indexed parameters have moved. There is no storage migration, and no nest's NID or registry hash changes. A swapped indexed parameter is refused, not misread An event's indexed markers decide which values come from topics and which from data. Swapping which parameter is indexed, at the same arity, keeps topic0 and the registry hash, so a reopened store and a compatible update reusing the old version's sealed segments trusted rows decoded under the other layout (#2157). A store now records each event…

      View evidence: v5.8.1 (opens in a new tab)

    2. v5.8.0nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.8.0 is the cold audit of 5.7.2 put right: the 107 verified defects and the follow-ups found while fixing them, across six sprints (#2110). Most of it is correctness of stored state, what one tenant can do to another, and what an untrusted caller can reach or leak.… Show all

      Nuthatch 5.8.0 is the cold audit of 5.7.2 put right: the 107 verified defects and the follow-ups found while fixing them, across six sprints (#2110). Most of it is correctness of stored state, what one tenant can do to another, and what an untrusted caller can reach or leak. There is no storage migration and no nest's NID or registry hash changes, but several defaults are stricter, and the ones that need an operator's attention before upgrading are listed at the end. Balances and exposure after a restart /balances and /exposure lost all but the last 10,000-row step of a large batch…

      View evidence: v5.8.0 (opens in a new tab)

  3. v5.7.2nuthatch-org/nuthatch

    GitHub releaseSource verified

    Nuthatch 5.7.2 moves init's output and a nest's identity into crates a browser tab can build, and names the chain head when an address-history range ends above it. There is no storage migration, and no nest's NID changes. init and the nest identity as their own crates The nest… Show all

    Nuthatch 5.7.2 moves init's output and a nest's identity into crates a browser tab can build, and names the chain head when an address-history range ends above it. There is no storage migration, and no nest's NID changes. init and the nest identity as their own crates The nest builder (RFC-0066) scaffolds and identifies a nest in a tab, so it needs init's own code rather than a copy. The NID, the data identity and the manifest move into nuthatch-identity (#2097); the contents of every file init writes, the semantic model and generate move into nuthatch-scaffold (#2098), with…

    View evidence: v5.7.2 (opens in a new tab)

  4. Code changes, week of 2026-10-12 – 2026-10-18 · 87 commitsnuthatch-org/nuthatch

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in nuthatch-org/nuthatch.

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

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 87 commits (opens in a new tab)

  5. v5.7.1nuthatch-org/nuthatch

    GitHub releaseSource verified

    Nuthatch 5.7.1 stops a quiet table's last rows from being held back from the mirror indefinitely, and moves the sealing rule into a crate a browser tab can build. There is no storage migration. A quiet table's tail is published within about three hours A table's last segment of… Show all

    Nuthatch 5.7.1 stops a quiet table's last rows from being held back from the mirror indefinitely, and moves the sealing rule into a crate a browser tab can build. There is no storage migration. A quiet table's tail is published within about three hours A table's last segment of under 1,000 rows is provisional: the table's next seal rewrites it, so publish sync holds it back. A table that gains rows slowly, or has stopped, stayed under that for good, so its newest rows never reached the mirror: on the DeFi Pulse nest, eth_usd__answer_updated held back eleven (#2084). A provisional tail…

    View evidence: v5.7.1 (opens in a new tab)

  6. 4 releases in nuthatch-org/nuthatch on 16 Oct

    GitHub release

    Show all 4 releases

    1. v5.7.0nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.7.0 keeps an address-history nest answering when one part of its backfill cannot, and says in /ready how far each kind of data is served. There is no storage migration. Both faults came from running rotki's validator support against a live mainnet nest, where a single… Show all

      Nuthatch 5.7.0 keeps an address-history nest answering when one part of its backfill cannot, and says in /ready how far each kind of data is served. There is no storage migration. Both faults came from running rotki's validator support against a live mainnet nest, where a single trace_filter window timed out on every poll. One failing window no longer stalls the nest A backfill window that failed marked the whole cursor stalled and was tried again every poll at the same cost, and block bodies and produced-block proofs waited behind every trace window (#2078). An address whose window…

      View evidence: v5.7.0 (opens in a new tab)

    2. v5.6.3nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.6.3 makes the SQL memo hold what it counts. There is no storage migration. The memo counted a seventh of what it held The /sql memo charges each remembered answer against its 64 MB ceiling (NUTHATCH_SQL_MEMO_BYTES). It charged the rows as serialized JSON but kept them… Show all

      Nuthatch 5.6.3 makes the SQL memo hold what it counts. There is no storage migration. The memo counted a seventh of what it held The /sql memo charges each remembered answer against its 64 MB ceiling (NUTHATCH_SQL_MEMO_BYTES). It charged the rows as serialized JSON but kept them as one JSON value per row, every column name allocated again in every row, and it kept the path of every sealed segment the answer read without charging for any of it (#2072). On a copy of the production allocations nest, 4,818 segments, a memo reporting 56 MB held about 410 MB of heap. An entry now keeps its…

      View evidence: v5.6.3 (opens in a new tab)

    3. v5.6.2nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.6.2 changes how the release is built, not what it builds. The binaries are the same code as 5.6.1 apart from a test. There is no storage migration. The release builds in parallel Each target used to link its default, scaled and graph binaries one after another in one… Show all

      Nuthatch 5.6.2 changes how the release is built, not what it builds. The binaries are the same code as 5.6.1 apart from a test. There is no storage migration. The release builds in parallel Each target used to link its default, scaled and graph binaries one after another in one job, so a tag took the sum of three fat-LTO links: 2 h 21 min for 5.3.1, the Mac default link alone 87 minutes. Each (target, variant) is now its own job, so a tag takes the slowest single link plus the image (#2068, #2035). The asset names are unchanged. The Mac build moves from macos-14, which GitHub retires on…

      View evidence: v5.6.2 (opens in a new tab)

    4. v5.6.1nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.6.1 gives each watched account its own backfill pace. There is no storage migration. One slow account no longer slows the rest The address-history backfill sizes its trace window by how long the last window took, and in 5.6.0 every account shared one pace (#2061). An… Show all

      Nuthatch 5.6.1 gives each watched account its own backfill pace. There is no storage migration. One slow account no longer slows the rest The address-history backfill sizes its trace window by how long the last window took, and in 5.6.0 every account shared one pace (#2061). An account whose traces were slow to fetch shrank the window for every other account in the nest, so a light account was backfilled in the heavy one's small steps and made far more trace_filter calls than it needed. Each account now keeps its own pace (#2063), kept across polls and started fresh on a restart. In the…

      View evidence: v5.6.1 (opens in a new tab)

  7. 3 releases in nuthatch-org/nuthatch on 15 Oct

    GitHub release

    Show all 3 releases

    1. v5.6.0nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.6.0 serves account history for several chains at one address, so rotki, which takes one indexer endpoint, can ask a single nuthatch dev about Ethereum, Base and Gnosis at once. There is no storage migration. One endpoint for several chains (RFC-0063 §14) Point… Show all
      • Nuthatch 5.6.0 serves account history for several chains at one address, so rotki, which takes one indexer endpoint, can ask a single nuthatch dev about Ethereum, Base and Gnosis at once. There is no storage migration. One endpoint for several chains (RFC-0063 §14) Point nuthatch dev --dir at a directory with no nuthatch.toml of its own and one subdirectory per chain, each an ordinary address-history nest (#2055):
      • /api answers as the nest chainid names. A chainid no nest serves answers NUTHATCH_UNSUPPORTED, which rotki reads as "ask another indexer for this chain".…
      View evidence: v5.6.0 (opens in a new tab)

    2. v5.5.0nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.5.0 serves account history on six more chains: Optimism, Base, Arbitrum, Polygon, BNB Chain and Gnosis, the chains rotki users are asked to buy explorer keys for. There is no storage migration. Account history without trace_filter (RFC-0063 §13) Address history found… Show all
      • Nuthatch 5.5.0 serves account history on six more chains: Optimism, Base, Arbitrum, Polygon, BNB Chain and Gnosis, the chains rotki users are asked to buy explorer keys for. There is no storage migration. Account history without trace_filter (RFC-0063 §13) Address history found an account's transactions with trace_filter. reth caps it at 100 blocks and replays every block it covers, 47 s per 100 on Base, and Polygon and Arbitrum do not serve it at all. On these six chains the nest now uses the balance residual instead (#2053):
      • Outgoing transactions are the blocks where the…
      View evidence: v5.5.0 (opens in a new tab)

    3. v5.4.1nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.4.1 corrects what the deposit sweep's feed counts as a deposit. In 5.4.0 every incoming row was one, including transfers that moved nothing. There is no storage migration. A deposit is value that arrived account/nuthatchDeposits and the sweep's webhook now carry an… Show all
      • Nuthatch 5.4.1 corrects what the deposit sweep's feed counts as a deposit. In 5.4.0 every incoming row was one, including transfers that moved nothing. There is no storage migration. A deposit is value that arrived account/nuthatchDeposits and the sweep's webhook now carry an incoming row only when it moved value to the address (#2051). These are still served by txlist, txlistinternal and tokentx exactly as Etherscan serves them, and are no longer deposits:
      • A failed transaction, isError 1. On 5.4.0, a reverted 5 ETH transfer to a watched contract on anvil appeared in the…
      View evidence: v5.4.1 (opens in a new tab)

  8. 3 releases in nuthatch-org/nuthatch on 14 Oct

    GitHub release

    Show all 3 releases

    1. v5.4.0nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.4.0 adds the deposit sweep (RFC-0064): an address-history nest that reads each block once for its whole watched set, so its cost is per block rather than per address, and delivers incoming transfers as one numbered feed with retractions when a reorg takes one back.… Show all

      Nuthatch 5.4.0 adds the deposit sweep (RFC-0064): an address-history nest that reads each block once for its whole watched set, so its cost is per block rather than per address, and delivers incoming transfers as one numbered feed with retractions when a reorg takes one back. Nothing about an existing nest changes. There is no storage migration. This minor is early. 5.x cuts features monthly, and this one was brought forward for a payment processor that asked on 2026-10-14 for a deposit indexer over hundreds of thousands of custody addresses (#2044). It adds and breaks nothing, which is all…

      View evidence: v5.4.0 (opens in a new tab)

    2. v5.3.3nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.3.3 lets an address-history backfill grow its windows over an RPC whose calls are slow whatever their range, and replaces a Polygon default endpoint that stopped serving logs. Nothing outside an [address_history] nest changes, apart from that one default. There is no… Show all
      • Nuthatch 5.3.3 lets an address-history backfill grow its windows over an RPC whose calls are slow whatever their range, and replaces a Polygon default endpoint that stopped serving logs. Nothing outside an [address_history] nest changes, apart from that one default. There is no storage migration. Fixes
      • A backfill over a slow RPC no longer stays at its smallest window. 5.3.2 let the pacer's target rise to three times a window's fixed cost, but still grew a window only when the whole window took under half that target. Over GraphOps, three eth_getLogs at about 1.5 s each put 4.5 s…
      View evidence: v5.3.3 (opens in a new tab)

    3. v5.3.2nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.3.2 makes an address-history nest's first backfill finish in minutes over a hosted RPC, and stops it reading every block body for accounts nobody asked about. Nothing outside an [address_history] nest changes. There is no storage migration. Fixes · A backfill over a… Show all
      • Nuthatch 5.3.2 makes an address-history nest's first backfill finish in minutes over a hosted RPC, and stops it reading every block body for accounts nobody asked about. Nothing outside an [address_history] nest changes. There is no storage migration. Fixes
      • A backfill over a remote RPC no longer crawls. Each window's checks cost about 2.3 s over Alchemy whatever the window's size, more than a quarter of the default 8 s request deadline, so the pacer halved the window to its 64-block floor and kept it there. One year of one wallet was heading for 12 hours. The pacer now tells a…
      View evidence: v5.3.2 (opens in a new tab)

  9. v5.3.1nuthatch-org/nuthatch

    GitHub releaseSource verified

    Nuthatch 5.3.1 keeps an address-history nest serving through a long pass, and refuses a timestamp or a cached transaction that belongs to another fork. Nothing outside an [address_history] nest changes. There is no storage migration. Fixes · A long pass no longer freezes the… Show all
    • Nuthatch 5.3.1 keeps an address-history nest serving through a long pass, and refuses a timestamp or a cached transaction that belongs to another fork. Nothing outside an [address_history] nest changes. There is no storage migration. Fixes
    • A long pass no longer freezes the head. A validator proof, a body scan or a slow beacon read held the cursor until it finished, so polls stopped and a tip request waited behind that one chunk. Polls now run during the pass, waiting requests are served between chunks, and a read that is still in flight yields every 50 ms.
    • **A beacon retry stays…
    View evidence: v5.3.1 (opens in a new tab)

  10. 3 releases in nuthatch-org/nuthatch on 11 Oct

    GitHub release

    Show all 3 releases

    1. v5.3.0nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.3.0 proves which blocks a validator proposed (RFC-0063 plan C), whoever received their fees, so rotki can book a validator's produced blocks and MEV from a nest alone. It also fixes a 5.2.0 defect that stopped rotki reading history from a nest with a start_block.… Show all
      • Nuthatch 5.3.0 proves which blocks a validator proposed (RFC-0063 plan C), whoever received their fees, so rotki can book a validator's produced blocks and MEV from a nest alone. It also fixes a 5.2.0 defect that stopped rotki reading history from a nest with a start_block. Nothing outside an [address_history] nest changes, and there is no storage migration. Proven proposers per validator (Ethereum mainnet)
      • The proof is the chain's own. Block N+1's parent_beacon_block_root (EIP-4788) commits to the beacon header that produced block N, whose proposer_index names the proposer.…
      View evidence: v5.3.0 (opens in a new tab)

    2. v5.2.0nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.2.0 makes address history (RFC-0063) meet rotki's sync on Ethereum mainnet: history up to the chain head on demand, reorgs taken back, and answers that are exact or refused. Nothing outside an [address_history] nest changes. An address-history store written by 5.1 is… Show all
      • Nuthatch 5.2.0 makes address history (RFC-0063) meet rotki's sync on Ethereum mainnet: history up to the chain head on demand, reorgs taken back, and answers that are exact or refused. Nothing outside an [address_history] nest changes. An address-history store written by 5.1 is moved aside intact and the history read again (see Compatibility). Two cold tests of 5.1.1, by testers with no build history, said not ready. Every item below answers one of their findings. RFC-0063 §12 has the reasoning. Exact or refused
      • An explicit endblock is answered whole or refused. 5.1.1 shortened…
      View evidence: v5.2.0 (opens in a new tab)

    3. v5.1.1nuthatch-org/nuthatch

      GitHub releaseSource verified

      Nuthatch 5.1.1 fixes address history (RFC-0063) off Ethereum and makes its backfill workable on providers that cap a call's block range. Nothing outside an [address_history] nest changes. There is no storage migration. Fixes · Optimism before Bedrock was served as an empty… Show all
      • Nuthatch 5.1.1 fixes address history (RFC-0063) off Ethereum and makes its backfill workable on providers that cap a call's block range. Nothing outside an [address_history] nest changes. There is no storage migration. Fixes
      • Optimism before Bedrock was served as an empty history (#2023). Its RPC answers trace_filter there with an empty success, so a pre-Bedrock range read as an address with no transactions. It now answers NUTHATCH_UNSUPPORTED and is never scanned. A 5.1.0 nest on Optimism that started before block 105,235,063 should be pointed at a fresh directory, since its…
      View evidence: v5.1.1 (opens in a new tab)

  11. Code changes, week of 2026-10-05 – 2026-10-11 · at least 377 commitsnuthatch-org/nuthatch

    Code activitySource linked

    What changed, in the repository’s own words:

    at least 7 active days in nuthatch-org/nuthatch since 2026-10-05; the count stops at the newest 100 commits listed.

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

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · at least 377 commits (opens in a new tab)

  12. v5.1.0nuthatch-org/nuthatch

    GitHub releaseSource verified

    Nuthatch 5.1.0 adds address history (RFC-0063): a nest that watches accounts rather than contracts, and serves their history at /api in Etherscan's shapes, so rotki can use it as an indexer. Nothing about an existing nest changes. There is no storage migration. This minor is a… Show all

    Nuthatch 5.1.0 adds address history (RFC-0063): a nest that watches accounts rather than contracts, and serves their history at /api in Etherscan's shapes, so rotki can use it as an indexer. Nothing about an existing nest changes. There is no storage migration. This minor is a month early. 5.x cuts features monthly, and this one was brought forward for rotki, whose founder agreed to a local indexer source on 2026-10-09 (rotki/rotki#13335). It adds and breaks nothing, which is all the policy asks of a minor. Address history (RFC-0063) A nuthatch.toml with an [address_history] table…

    View evidence: v5.1.0 (opens in a new tab)

  13. Code changes, week of 2026-10-05 – 2026-10-11 · 72 commitsnightswatchhq/nuthatch-frontend

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in nightswatchhq/nuthatch-frontend.

    This week HEY looked inside 5 of 72 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.

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

  14. Code changes, week of 2026-10-05 – 2026-10-11 · at least 203 commitsnightswatchhq/nuthatch

    Code activitySource linked

    What changed, in the repository’s own words:

    at least 5 active days in nightswatchhq/nuthatch since 2026-10-05; the count stops at the newest 100 commits listed.

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

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · at least 203 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 Nuthatch Org? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

130 changes on HEY’s record for Nuthatch Org: 99 releases · 16 official source changes · 3 build pace changes · 12 weeks of code pushed.

All 130 changes for Nuthatch Org →

The full change record holds 15 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 9 of the 10 research questions that apply.

9 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 4h ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 30m ago.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesMeasuredRead 8d ago.

Code and packages

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

10 more sources (docs)