Ecosystem metrics

New Repos
15
New
Commits
850
down 13.9%
Releases
6
down 25.0%
Contributors
46
down 14.8%
Merges
33
down 25.0%

Repository Explorer

6958 commits in all time Jun 04, 2026 14:33 – Sep 02, 2026 14:33 UTC
Merge 1be72685f34143f116bbb9294ebc8290bf78d92c into 7fdd08948797fd0e5517f8e7ed0ec0ed65d7fa22
Git Commit af74b831 Branch pull/5/merge Document 2/203 ++ 8 --
Merge bb94c9045d36ead209dc04a008d1b3c40940ac45 into 543110998c63b82a7f517c631c32ae62b9fbe9e3
Git Commit 6318f107 Branch pull/944/merge Document 59/4,215 ++ 156 --
feat: reject extension property collisions and freeze base provider identity
Git Commit 1be72685 Branch pull/5/head Document 2/203 ++ 8 --
mrcointreau algokit-lora
Merge c0c3413506e4dee3542755d4171edcf80c44d23b into 0e26b4b274a282ae273b68b29140379d39803971
Git Commit 4ae939e7 Branch pull/602/merge Document 141/2,476 ++ 2,807 --
joe-p algokit-lora
chore: fixes from claude code review
1. .nsprc — restored expiry-based suppressions

  Converted all entries back to the object form with
active/expiry/notes, expiring 2027-03-01, and re-added the elliptic
advisory (1112030) that had been dropped. The audit
  still passes with no "unused exception" warning, so carrying elliptic
is free and means the file stays complete if the gate is ever tightened
from moderate to low.

  2. block-result.ts:38 — restored proposer?.toString()

  One line, closing the gap between the string type and the Address
instance algosdk actually decodes.

  3. state-delta-mappers.ts:157,173 — corrected "global" → "local" in
asLocalStateDeltaItem
Git Commit c0c34135 Branch chore/v9-revert-and-modernize Document 3/83 ++ 17 --
joe-p algokit-lora
chore: fix react-router-dom patch
Git Commit f13159ed Branch chore/v9-revert-and-modernize Document 1/27 ++ 28 --
joe-p algokit-lora
chore: npm audit
Git Commit 88b3f191 Branch chore/v9-revert-and-modernize Document 4/173 ++ 59 --
Update src/main/java/com/algorand/algosdk/signer/Ed25519MultisigAlgorandSigner.java
Co-authored-by: mrcointreau <45950216+mrcointreau@users.noreply.github.com>
Git Commit 0bc4439c Branch pull/944/head Document 1/3 ++ 3 --
Update src/main/java/com/algorand/algosdk/signer/Ed25519AlgorandSigner.java
Co-authored-by: mrcointreau <45950216+mrcointreau@users.noreply.github.com>
Git Commit a6d691e9 Branch pull/944/head Document 1/2 ++ 3 --
Update src/test/java/com/algorand/algosdk/crypto/TestPQ.java
Co-authored-by: mrcointreau <45950216+mrcointreau@users.noreply.github.com>
Git Commit bb94c904 Branch pull/944/head Document 1/13 ++ 4 --
cusma specs
Merge a699bd31702b01fbea5c5e36fdccd59bc3015119 into 0efa5540886f64438b9045faa6e4eba73edefa67
Git Commit 09c36d33 Branch pull/311/merge Document 11/433 ++ 351 --
yasincaliskan connect
chore: upgrade walletconnect to 1.0.2 and bump to 1.6.1 (#207)
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Git Commit 4b7d97f1 Branch main Document 2/13 ++ 13 --
urtho pg_algorand
Add PREFIX_INDEX_DESIGN.md: note-prefix index design brief and rollout notes
Sections 1-6 are the original brief (problem, verified facts, design,
milestones, acceptance). Section 7 records how the 2.1 implementation
departed from the brief (planner hook instead of a support function) and
section 8 the first production deployment with measurements and the
plan-cache finding fixed in 4faf1f5. Host names, paths and other
environment specifics are left out.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BAkGJyPG5VRajhBwFRPiQ2
Git Commit 43137a99 Branch main Document 1/269 ++ 0 --
cusma specs
Merge pull request #315 from algorandfoundation/dependabot/github_actions/minor-and-patch-6512b1d693
chore(deps): bump softprops/action-gh-release from 3.0.2 to 3.0.3 in the minor-and-patch group
Git Commit 0efa5540 Branch master Document 1/1 ++ 1 --
ipaleka widgets
Added interface state function to the Dust Sweep, carrying the page context it must not lose
Git Commit 651b8db4 Branch main Document 2/71 ++ 5 --
Merge 9be87680abc7b2382309a6ab0ddfba3170b83127 into 627d1244dff8307c0f9afe0462db55dd06ef6f9e
Git Commit 8cdc8d83 Branch pull/611/merge Document 2/132 ++ 4 --
urtho pg_algorand
2.1: keep prepared statements with N < K prefix clauses on custom plans
With server-side prepared statements the plan cache builds a generic plan
after five executions. For substring(x,1,N) = $1 with N smaller than the
index prefix K, no value is available at plan time, so nothing can be
derived and the plan falls back to an unindexed scan. Under LIMIT with
default selectivity that scan is estimated cheap (cost ~12k on mainnet vs
the real crawl over billions of rows), so plancache adopts it and the
prefix index is never used again for that statement.

The hook now adds a large penalty to the total cost of any plan built with
an unbound external Param on a N < K prefix clause, which is exactly the
generic-plan case. plancache compares that against the average custom plan
cost and keeps replanning with the actual value, where the range on the
prefix index is derived as before. N >= K statements are unaffected.

Observed on the ush mainnet indexer: EXPLAIN EXECUTE x7 for N=3 switched
from the index range scan to a txn_pkey filter on the sixth execution.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BAkGJyPG5VRajhBwFRPiQ2
Git Commit 4faf1f58 Branch main Document 4/102 ++ 4 --
fix: resolve transaction IDs from the signed transactions
Signers (e.g. wallets) can mutate the transactions they are given, so
the built transactions aren't necessarily the ones that reach the network. The
mutated group was sent successfully, but `send()` then waited for confirmation of
the pre-mutation transaction ID, which is never found. The reported `txIds`,
`transactions` and `groupId` were stale for the same reason, in both `send()` and
`simulate()`.

Read the transactions back out of the signed transactions instead. The built
transaction is kept when its ID is unchanged.
Git Commit 9be87680 Branch fix/mutated-transactions-txids Document 2/132 ++ 4 --
d13co algokit-utils-ts
fix: resolve transaction IDs from the signed transactions
Signers (e.g. wallets) can  mutate the transactions they are given, so
the built transactions aren't necessarily the ones that reach the network. The
mutated group was sent successfully, but `send()` then waited for confirmation of
the pre-mutation transaction ID, which is never found. The reported `txIds`,
`transactions` and `groupId` were stale for the same reason, in both `send()` and
`simulate()`.

Read the transactions back out of the signed transactions instead. The built
transaction is kept when its ID is unchanged, as decoding is lossy for zero
valued fields (a built `fee` of `0n` decodes back as `undefined`).
Git Commit ed94bf86 Branch fix/mutated-transactions-txids Document 2/132 ++ 4 --
yasincaliskan connect
Merge 1b9824baffc77956a659e647f4aaf57904fabfe0 into 86024725aa0a8471e230a4b16401e2cc8a970d84
Git Commit dbbea45a Branch pull/207/merge Document 2/13 ++ 13 --
yasincaliskan connect
chore: bump version to 1.6.1
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Git Commit 1b9824ba Branch yasincaliskan/bump-walletconnect-1.0.2 Document 1/1 ++ 1 --
giuliop go-algorand
Merge 4aea623fbb7868f304cc13eee925812be8258d87 into 42f70fe22bf79c104ddc289fd1a33168009803cf
Git Commit 7df16d19 Branch pull/6723/merge Document 13/505 ++ 12 --
giuliop go-algorand
Improve logicSigAllowances comment
Git Commit 4aea623f Branch safer-logicsigs Document 2/31 ++ 2 --