Ecosystem metrics

New Repos
4
New
Commits
450
down 42.4%
Releases
7
up 0.0%
Contributors
42
down 10.6%
Merges
12
down 29.4%

Repository Explorer

6940 commits in all time Jun 12, 2026 18:24 – Sep 10, 2026 18:24 UTC
Merge f2f4ca7ce8653529304f2dadc3b1a826221e47ad into 361d3066ffaca4241991cc6563403417bf562ecf
Git Commit f05479f7 Branch pull/23/merge Document 1/4,209 ++ 3,554 --
Merge ef819262d2fe9ca8f564d0b5abc5f2f5123ea7bc into 361d3066ffaca4241991cc6563403417bf562ecf
Git Commit 6335ab01 Branch pull/17/merge Document 4/3,364 ++ 1,957 --
Merge 5605fa9bfa7e4474089bbf551e86b9a747b2f91a into 243ec8e4e1377526ce85f5821ee29caf4dfc0d7f
Git Commit 8a31d125 Branch pull/408/merge Document 5/50 ++ 18 --
joe-p go-algorand-sdk
Merge b9d2bb3eb9c6d6eb97c83c3e6c4daa6358fc7de1 into cec61858e02e3d46d044b9cfc67997fdd64d39d3
Git Commit f510128d Branch pull/845/merge Document 36/1,103 ++ 669 --
joe-p go-algorand-sdk
chore: remove non-canonical salt support
Git Commit b9d2bb3e Branch joe-p/pqsig-support Document 10/122 ++ 173 --
scholtz wallet
Merge 93e388216e20efce71ff966cf27427a53281755a into 978e6d819af06b0308951824d5ffabaa0fe2a09b
Git Commit b108a6dc Branch pull/169/merge Document 29/2,358 ++ 208 --
scholtz-aures wallet
feat: connect to dApps with Liquid Auth (passkey-linked WebRTC, ARC-27 + ARC-60)
Adds a second dApp transport next to WalletConnect, following the Algorand
Foundation's Liquid Auth protocol: the wallet registers/uses a passkey at a
Liquid Auth service with the "liquid" extension (service challenge signed by
the account key, linked to the dApp's requestId), then negotiates a direct
WebRTC data channel (public Google STUN) and answers ARC-0027 messages:
arc0027:sign_transactions (ARC-0001) and the arc0060:sign_data extension.

- src/scripts/liquid/protocol.ts: ARC-0027 CBOR+base64url envelope, deep links
  (mirror of the codec in biatec-wallet-use-wallet-client)
- src/scripts/liquid/webauthn.ts: attestation/assertion ceremonies
- src/shared/liquid.ts: signaling socket + RTCPeerConnection per pairing,
  presence-driven renegotiation
- src/store/liquid.ts: sessions, requests, responses, ARC-60 domain checks
- src/shared/decodeSignRequests.ts: request decoders extracted from wc.ts and
  shared by both transports (accept base64 and base64url)
- signer/signLiquidChallenge (sk + HD accounts), liquid/reset on logout
- Connect page: "Liquid Auth" tab; request tables take a `namespace` prop
- docs/LIQUID_AUTH.md: protocol summary, trust model, service deployment
  (RP ID must be the wallet's domain, CORS with credentials)
- locales: connect.liquid.* in all languages (English text for now)
- playwright/unit/liquidProtocol.spec.ts

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Git Commit 93e38821 Branch feat/liquid-auth Document 29/2,358 ++ 208 --
Steve0x2a algokit-lora
Merge 838ba5882277ed8c5ce3cc95bc9b4a0808fc9290 into b1b7fa4eb7ed799efdc5b47683f7206c041e2fee
Git Commit 6823dd41 Branch pull/611/merge Document 2/28 ++ 0 --
chore: bump org.jetbrains.kotlin.jvm from 2.4.10 to 2.4.20 in /HaveAMagicalDay (#372)
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Git Commit e6b86e9d Branch main Document 1/1 ++ 1 --
chore: bump org.jetbrains.kotlin.jvm in /HaveAMagicalDay
Bumps [org.jetbrains.kotlin.jvm](https://github.com/JetBrains/kotlin) from 2.4.10 to 2.4.20.
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.4.10...v2.4.20)

---
updated-dependencies:
- dependency-name: org.jetbrains.kotlin.jvm
  dependency-version: 2.4.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Git Commit 2b12bb23 Branch pull/372/head Document 1/1 ++ 1 --
daniel-makerx puya
Merge b6479fac1a27a2ead1ba504eb558ea0b50288fd3 into 27751c364229ae3cd0334fe4071e61690b6879e4
Git Commit a87ec5d2 Branch pull/733/merge Document 300/35,080 ++ 32,067 --
tasibot nodekit
Merge b85ac9bb1c0c0847fb3aca3b86e0cefa6087d76e into 0406606800d1809fe7d75492aec2b06cd5ea4412
Git Commit 85977cc0 Branch pull/193/merge Document 37/4,831 ++ 12 --
tasibot nodekit
docs: add the generated man page for logs
Every other registered top-level command has one, and the README's
command list is where the published docs link from. Generated with
cobra/doc and put through the same banner substitution the existing
pages carry, checked by regenerating nodekit_restart.md and diffing it
against the committed copy.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMKTAqwAPrGqB8hvgmBWu5
Git Commit b85ac9bb Branch pull/193/head Document 2/51 ++ 0 --
tasibot nodekit
docs: state that --since bounds the region read
The decision record still listed stopping the backward walk early on
--since as deliberately deferred, on the grounds that it would change
what the flag means for entries Keep never drops on time. Three
optimizations went in since and do exactly that: the walk stops once a
chunk's oldest line is older than the bound, a forward stream bisects to
the first entry at or after it, and an archive written entirely before
it is not opened at all, which is the only way to skip a compressed one.
Reviewers of #193 read the record against the code and found the
contradiction three times over, once per site.

The record was the stale half. --since bounds the region of the history
that is read, and an entry whose timestamp cannot be read is shown when
it falls in that region: a panic dump belongs to the moment the lines
around it were written, and one from two hours ago is not part of the
last fifteen minutes. Written down as a decision, with the reasoning
alongside the cost the three optimizations avoid, and cross-referenced
from each of them and from Filter.Keep. The sentence in sinceOffset
calling its answer "never a filter" was the specific claim that had
stopped being true.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMKTAqwAPrGqB8hvgmBWu5
Git Commit ce43608a Branch pull/193/head Document 4/27 ++ 5 --
tasibot nodekit
fix: parse in full when --filter text contains <, > or &
The prescreen searches the undecoded line for the filter text verbatim,
which is only sound for bytes JSON never rewrites. Quotes, backslashes
and non-ASCII were excluded on that basis; `<`, `>` and `&` were not,
and they should have been. logrus writes its JSON through Go's encoder
with HTML escaping left on, so where the decoded message holds one of
those characters the line holds \u003c, \u003e or \u0026. `nodekit logs
--filter '<nil>'` therefore found nothing, however many entries said
<nil>.

Those three bytes now fall through to the full parse, along with the
rest of the text the raw search cannot be trusted on.

The corpus line and the two filters added to the one-sided prescreen
test fail without the fix.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMKTAqwAPrGqB8hvgmBWu5
Git Commit 3c245bc5 Branch pull/193/head Document 2/16 ++ 3 --
tasibot nodekit
fix: bound the reader against a shrinking file and a runaway line
Two problems in reader.go, both raised in review of #193.

The backward walk sized the file, then read chunks of it with ReadAt and
ignored the count returned. A file truncated in place or replaced by a
shorter one after that stat hands back a short read with io.EOF, leaving
the tail of the buffer zeroed; those NUL bytes were then split into
lines, parsed as entries and charged against the scan budget. The walk
now takes only the bytes actually read, and drops the carry from the
chunk above with them, since the two halves no longer abut and splicing
them would invent a line neither file contains.

Follow read its lines with ReadBytes, which accumulates until it finds
the delimiter. The cap below it only ever saw a line that had already
been buffered whole, so a runaway line was bounded by the writer rather
than by us. It now reads the way forEachLine does, keeping at most
maxLineBytes across ErrBufferFull and discarding the rest, which is
where ParseLine would have sent it anyway.

The stale-size test fails without the first fix, emitting a 384-byte
entry of NULs. The follow test does not discriminate on output, since
the old path arrived at the same truncation by a more expensive route;
it guards the part of the rewrite that could go wrong, that the
discarded remainder does not disturb the line after it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMKTAqwAPrGqB8hvgmBWu5
Git Commit d09a2a2f Branch pull/193/head Document 2/87 ++ 16 --
chore: bump kotlin from 2.4.10 to 2.4.20 in /DisneyScenicRides (#371)
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Git Commit efa3719e Branch main Document 1/1 ++ 1 --
meetthosar devportal
Merge 0d7ec359165f4d90c835d52579da21af92c4e2b0 into 098098e5f2f22f9f23b8e43df19fdf220f6112ca
Git Commit 5ce3dbb1 Branch pull/662/merge Document 7/28 ++ 11 --
meetthosar devportal
Merge 7ceca54cde38b2174f82ea2ab947b55f93905477 into 098098e5f2f22f9f23b8e43df19fdf220f6112ca
Git Commit a6ae9173 Branch pull/661/merge Document 2/3 ++ 7 --
chore: bump kotlin from 2.4.10 to 2.4.20 in /DisneyScenicRides
Bumps `kotlin` from 2.4.10 to 2.4.20.

Updates `org.jetbrains.kotlin:kotlin-gradle-plugin` from 2.4.10 to 2.4.20
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.4.10...v2.4.20)

Updates `org.jetbrains.kotlin.plugin.compose` from 2.4.10 to 2.4.20
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.4.10...v2.4.20)

---
updated-dependencies:
- dependency-name: org.jetbrains.kotlin:kotlin-gradle-plugin
  dependency-version: 2.4.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.jetbrains.kotlin.plugin.compose
  dependency-version: 2.4.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Git Commit 0b45b55e Branch pull/371/head Document 1/1 ++ 1 --
chore: sync stable release 2.4.1 to main [skip ci]
This commit syncs the stable release version back to main branch
to ensure the next beta cycle starts from the correct version base.

Release: 2.4.1
Tag: v2.4.1
Git Commit b1b7fa4e Branch main Document 3/9 ++ 3 --
chore(release): ref:stable 2.4.1 [skip ci]
## [2.4.1](https://github.com/algorandfoundation/algokit-lora/compare/v2.4.0...v2.4.1) (2026-09-10)

### 🐛 Bug Fixes

* use utils 9.2.2 to work with Pera's PQ fee changes ([#609](https://github.com/algorandfoundation/algokit-lora/issues/609)) ([7461262](https://github.com/algorandfoundation/algokit-lora/commit/746126278c85c16b1da5c8570e0e156aafb24de4))
Git Commit 127138e8 Branch release Document 3/9 ++ 3 --