Ecosystem metrics

New Repos
12
New
Commits
472
down 33.0%
Releases
6
down 25.0%
Contributors
48
down 2.0%
Merges
12
down 29.4%

Repository Explorer

7108 commits in all time Jun 13, 2026 21:00 – Sep 11, 2026 21:00 UTC
tasosbit nodekit
Merge pull request #194 from ChrisWozniak/fix/issue-189-upgrade-success-messages
fix: add upgrade success messaging
Git Commit 884eebf7 Branch v1.7 Document 1/6 ++ 0 --
Merge e8b8529337ef4f5daea93fd499531c9ea24274ea into 243ec8e4e1377526ce85f5821ee29caf4dfc0d7f
Git Commit ee4c0e51 Branch pull/408/merge Document 13/694 ++ 568 --
joe-p algokit-utils-ts
fix: propagate createParams
Git Commit 5656fe05 Branch feat/schema_epp_changes Document 2/29 ++ 4 --
joe-p algokit-utils-ts
chore: bump algosdk
Git Commit b2e17fc1 Branch feat/schema_epp_changes Document 2/5 ++ 5 --
joe-p algokit-utils-ts
feat: ensure epp and schema changes are respected everywhere
Git Commit c7f757ae Branch feat/schema_epp_changes Document 6/63 ++ 11 --
joe-p algokit-utils-ts
chore: npm audit
Git Commit 52ce2bbb Branch feat/schema_epp_changes Document 3/212 ++ 674 --
Merge df3d5a83a110c7dc0e73b0ec97138dc240f69fec into 243ec8e4e1377526ce85f5821ee29caf4dfc0d7f
Git Commit 8418b3b0 Branch pull/408/merge Document 13/713 ++ 567 --
ChrisWozniak nodekit
Merge 3ba4579524e36ed8a78f7d3631c29604b4e83fc3 into f40ba97e346ad7408168cc0b2e2ebaf4b8770e00
Git Commit 5a3b8431 Branch pull/196/merge Document 2/43 ++ 1 --
chris-wozniak nodekit
fix: support DNF 5 repository setup
Git Commit 3ba45795 Branch pull/196/head Document 2/43 ++ 1 --
ChrisWozniak nodekit
Merge cfaac69ccfdbba5b5ca2c7c89c74d3eee1d42b47 into f40ba97e346ad7408168cc0b2e2ebaf4b8770e00
Git Commit d8045a93 Branch pull/195/merge Document 2/47 ++ 3 --
chris-wozniak nodekit
fix: show date only for distant expirations
Git Commit cfaac69c Branch pull/195/head Document 2/47 ++ 3 --
ChrisWozniak nodekit
Merge 33b001e9b0a56492cbf055f7550991b842d4aaa4 into f40ba97e346ad7408168cc0b2e2ebaf4b8770e00
Git Commit 01a47cdb Branch pull/194/merge Document 1/6 ++ 0 --
chris-wozniak nodekit
fix: address upgrade messaging review feedback
Git Commit 33b001e9 Branch pull/194/head Document 2/7 ++ 66 --
Merge 0fda902b8ff007fccfb8efb0b238d5e67d47e3d2 into 361d3066ffaca4241991cc6563403417bf562ecf
Git Commit 78b0446b Branch pull/30/merge Document 2/310 ++ 111 --
fix(deps): update dependency next to v15 [security]
Git Commit 0fda902b Branch renovate/npm-next-vulnerability Document 2/310 ++ 111 --
mrcointreau algokit-lora
Merge b860e4a23a355e889484f621d55604a5e0f6d029 into b1b7fa4eb7ed799efdc5b47683f7206c041e2fee
Git Commit 83d0de2b Branch pull/614/merge Document 27/311 ++ 0 --
mrcointreau algokit-lora
feat: add 'lease' field to the transaction wizard
Git Commit b860e4a2 Branch feat/transaction-wizard-lease Document 27/311 ++ 0 --
JBScaled devportal
Merge pull request #665 from algorandfoundation/chore/remove-arc-52
chore: remove ARC52 mention
Git Commit f599fe0b Branch main Document 1/1 ++ 1 --
tasibot nodekit
Merge 1c62edc1ce24079e61b38e0fae75549ac10c1dee into 0406606800d1809fe7d75492aec2b06cd5ea4412
Git Commit a46c2821 Branch pull/193/merge Document 38/5,348 ++ 36 --
tasibot nodekit
fix: keep a field value from breaking an entry across two lines
A string field was quoted only when it held a space or an equals sign,
so a value carrying a newline and neither was written out raw and split
one entry over two lines, which is exactly what Render promises not to
do and what makes the output greppable.

Nothing algod writes reaches this today: a stack trace goes into the
message, where collapseNewlines handles it, and the one structurally
multi-line field is built by a telemetry hook on a copy of the entry
that never reaches the file. The guarantee is Render's own, though, and
--file points the command at whatever file the user names, so the test
now covers control characters, quotes and backslashes alike -- %q
escapes them together and the guarantee stops depending on the producer.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PqPSx1wqM8rMdo4EHPa4jy
Git Commit 1c62edc1 Branch pull/193/head Document 2/35 ++ 2 --
tasibot nodekit
fix: stop a pruned archive turning into a node that never logged
reportEmptyLogResult counted the sources the scan opened, which is the
list after PruneSources has already run. A --since newer than every
archive collapsed that count to the live log alone, so an empty live log
reported "the log file is empty, the node has not logged anything yet"
against a node with a year of rotated history behind it -- and sent the
user off to *start* a node that was already running.

The count is now the unpruned history, which leaves LogsNoMatchMsg to
explain the result. That is also the true answer: an archive pruned for
predating --since held nothing the search wanted either.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PqPSx1wqM8rMdo4EHPa4jy
Git Commit fae5a153 Branch pull/193/head Document 2/94 ++ 5 --