Ecosystem metrics
- New Repos
- 8
- down 68.0%
- Commits
- 960
- up 21.2%
- Releases
- 11
- up 83.3%
- Contributors
- 60
- up 30.4%
- Merges
- 17
- down 22.7%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
10597 commits in all time
May 15, 2026 13:28 – Aug 13, 2026 13:28 UTC
Merge 5695187443e6389ab496e4e54231b43f6bf89d30 into c89215d7048708c6f19274cb813911144da93eaa
0089d946
pull/836/merge
40/1,602 ++ 607 --
chore: Remove internalFalcon1024Signer (use SaltedFalcon1024Signer instead)
56951874
extensible-signing-api
1/2 ++ 16 --
Merge 0b9b1f7b96ca888ce9de51388522b0ffeff1b276 into ce7e081d5e7796d44bbfa79e0fe0350598ae814c
505a5a19
pull/205/merge
4/58 ++ 17 --
fix: label data-signing failures as SIGN_DATA instead of SIGN_TRANSACTIONS
0b9b1f7b
yasincaliskan/PERA-4866
4/58 ++ 17 --
Merge c3943f4811003219d22ec23e880f3b5a94c5fbcf into ce7e081d5e7796d44bbfa79e0fe0350598ae814c
ab1bedb3
pull/204/merge
3/152 ++ 10 --
fix: wake Pera via same-tab navigation so iOS Safari keeps the dApp page intact
c3943f48
yasincaliskan/PERA-4876
3/152 ++ 10 --
Merge 794a8b3e3241235f9179230d00eec984faab046c into 361d3066ffaca4241991cc6563403417bf562ecf
67a982e1
pull/32/merge
2/346 ++ 520 --
chore(deps): update commitlint monorepo to v21
794a8b3e
renovate/major-commitlint-monorepo
2/346 ++ 520 --
fix: trust Homebrew tap before install/upgrade
Homebrew 6.0 refuses to load formulae from taps that have not been explicitly trusted. Run 'brew trust algorandfoundation/node' before installing or upgrading algorand. The command is best-effort since 'brew trust' only exists from Homebrew 5.1.15 onward.
525df29b
pull/186/head
1/22 ++ 0 --
docs: refresh appendix block fields from review fixes
Regenerated from the go-algorand PR 6690 review changes: genesis blocks start their txn counter at 1000, and the block fields no longer describe the zero values returned for blocks that predate their enabling upgrade.
21a7f33f
pull/314/head
1/5 ++ 5 --
Merge b3a2fcab66d4311f87b34debbccbf4a6ed8091e7 into 8d7f8f778c8668bb5162fad3179bbb4cbb1082bb
7a9d7399
pull/6690/merge
39/2,216 ++ 3,884 --
Merge 2130c2fd0826b5e8b15d16979455b15a4a5e8a19 into f63cce5c51a360d3f8d685268de440430347b5cb
bbb0a15e
pull/596/merge
8/345 ++ 63 --
Merge 9130a0c70e4d4613a2f2ecdd57f5741635cd2308 into 95d55a9b81145fcbc0a09023680b96b684f57b64
f63cce5c
pull/595/merge
36/2,629 ++ 67 --
refactor: rename *TransactionSigner callback signers to *AlgorandSigner
9130a0c7
feat/pq
7/82 ++ 88 --
Doc: Note that booleans behave like null at json_ref extraction
The Special Values section listed booleans and null separately, which read as though they differ at extraction. They do not: extracting a key whose value is true, false, or null errors whatever return type is requested. Booleans are never readable as JSONString letters or JSONUint64 0 and 1. Merge the bullets, and add the missing extraction coverage to TestOpJSONRef for all three values across all three return types.
b3a2fcab
pull/6690/head
2/34 ++ 3 --
Doc: Drop the historical-zero notes from the block fields
BlkProposer, BlkFeesCollected, BlkBranch512, and BlkSha512TxnCommitment described the zero values returned for blocks that predate their enabling upgrade. Per review, the docs describe the behavior of the current protocol, and these transition notes were not applied consistently across fields anyway.
34bcedd6
pull/6690/head
7/20 ++ 20 --