Ecosystem metrics

New Repos
12
down 99.4%
Commits
777
up 10.5%
Releases
8
down 11.1%
Contributors
51
down 3.8%
Merges
36
up 71.4%

Repository Explorer

6243 commits in all time May 27, 2026 04:38 – Aug 25, 2026 04:38 UTC
Merge 605843cdc107b8483ab3f1af1245abdec6633def into b0a3e71a91adfd1dfb97b5060d054618c2a147aa
Git Commit 16e2f2fa Branch pull/66/merge Document 10/1,152 ++ 1,265 --
Merge e1ca4a9838012381efd3e871a89d5fd94d0a99d4 into 9bc334a8819e21a61e5717e04c07dec184a7c579
Git Commit aa5d946c Branch pull/92/merge Document 2/34 ++ 36 --
chore(deps): update dependency eslint to v10
Git Commit e1ca4a98 Branch renovate/major-eslint-monorepo Document 2/34 ++ 36 --
Merge 03489046fcf5cf76a464c83b0fa727eca2748069 into 8602e0430cdc499f3bc1cecc5abe4aa31f4aee44
Git Commit 16c91209 Branch pull/172/merge Document 86/9,662 ++ 8,186 --
ipaleka widgets
Added asastats smart router widget
Git Commit 0bbd4a48 Branch main Document 8/192 ++ 31 --
Merge 0bb0da842c0150f758d607b366af6478951d1995 into 8602e0430cdc499f3bc1cecc5abe4aa31f4aee44
Git Commit 2e971e25 Branch undefined Document 85/9,658 ++ 8,186 --
Merge 6d970fc84629c1878dd0e835c9ec57a26c6814a1 into 543110998c63b82a7f517c631c32ae62b9fbe9e3
Git Commit d8f7f466 Branch pull/944/merge Document 59/4,233 ++ 156 --
algorandskiy go-algorand
Merge d39f331ceea2c7c870e72240f425f5c8991c5894 into dd6de88fbe0e01cb913142453c858b98cecdf97c
Git Commit 0e225d29 Branch pull/6711/merge Document 4/260 ++ 38 --
joe-p algokit-utils-ts
Merge 3d63d70102a1684a0fbdea0777dfd8a28c0a182d into fb8247d1111a5c618a32185104e0b6efd00c0f77
Git Commit 5032d0e6 Branch pull/608/merge Document 13/127 ++ 47 --
joe-p algokit-utils-ts
Merge caf52aac315ce4040946d64d8e7339366c67c4be into fb8247d1111a5c618a32185104e0b6efd00c0f77
Git Commit d9388c51 Branch undefined Document 12/116 ++ 29 --
joe-p algokit-utils-ts
chore: npm audit
Git Commit caf52aac Branch feat/schema_epp_changes Document 1/2 ++ 2 --
joe-p algokit-utils-ts
Merge b9030cb0797f66841d611e75d0cc76d23d5b67f9 into fb8247d1111a5c618a32185104e0b6efd00c0f77
Git Commit f6a2f9e0 Branch undefined Document 11/114 ++ 27 --
joe-p algokit-utils-ts
feat: allow schema and extra page changes through deployer
Git Commit b9030cb0 Branch feat/schema_epp_changes Document 11/114 ++ 27 --
Merge 22d96fb58db93dbd3252c425fe34b3e214a393b2 into 543110998c63b82a7f517c631c32ae62b9fbe9e3
Git Commit f90eccd0 Branch pull/942/merge Document 26/1,223 ++ 146 --
Merge pull request #947 from algorand/release/2.11.0
FOR REVIEW ONLY: java-algorand-sdk 2.11.0 changelog and version bump
Git Commit 54311099 Branch main Document 3/13 ++ 2 --
semantic-release puya
5.10.1
Automatically generated by python-semantic-release
Git Commit 27751c36 Branch main Document 4/9 ++ 45 --
Merge 1910b627c1c556580229ffc52213dbb3a8c969f3 into f20a5b93e8a0ad031da9512281b92f82c615f024
Git Commit 9edd3a00 Branch undefined Document 3/13 ++ 2 --
joe-p java-algorand-sdk
docs: manually write changelog
Seems to have been a bug in the changelog generator, so I have manually
written the notes using the same format
Git Commit 1910b627 Branch main Document 1/9 ++ 2 --
joe-p java-algorand-sdk
feat: v42 models and dry run removal (#946)
* Regenerate code from specification file

* feat: remove dry run due to removal in algod

* WIP: ignore falcon tags

Should ideally merge
https://github.com/algorand/algorand-sdk-testing/pull/327 first so we
can continue to use master

* test: revert algorand-sdk-testing branch to master

This will fail CI until
https://github.com/algorand/algorand-sdk-testing/pull/327 is merged

---------

Co-authored-by: Algorand Generation Bot <codegen@algorand.com>
Git Commit f20a5b93 Branch main Document 35/397 ++ 898 --
tasosbit gGov
chore: format
Git Commit 3bd5b79e Branch feat/avm13-computed-pages Document 1/1 ++ 1 --
tasosbit gGov
feat: registries open their boxes to foreign reads at create
AVM v13 relaxes box isolation: an app can opt its boxes into reads by any other
app. Both registries now do that in a new createApplication, which runs
app_params_set(appForeignBoxReads, true). Verified on localnet that the opcode is
permitted during the creating call itself, so no separate post-create step is
needed - the v13 notes describe enabling access as update-then-run, but that is
for apps already deployed.

Reads only; writes stay exclusive to the owning app. app_params_set is run by an
app on itself, so a contract that is not updatable can never opt in later, which
is what preserves intentional immutability.

The create is a real ABI method rather than a bare one. It lands in the ARC-56 and
the generated clients, it can take arguments later without changing the create
shape a second time, and it matches the house style - FracDelegationInstance
already has an ABI createApplication invoked by selector from the registry
factory. Both createRegistry paths switch from create.bare() to the method call;
every other caller routes through createRegistry.

Two consequences of the create no longer being bare, both found by the suite:

- deployRegistryWithoutBytecode in the period e2e spec deploys a registry
  directly and was still doing a bare create, which is no longer routed and fails
  with an err on the OnCompletion match.

- The ATST unit specs. ATST holds a contract with any create method in
  `isCreating` and rejects every ABI call with "method can not be called while
  creating" until a create method runs - but ATST 1.2.0 predates v13 and cannot
  execute app_params_set, so the real body cannot run in the emulator. The
  registry test subclass overrides createApplication with a no-op and calls it
  after construction; the opt-in itself is covered e2e.

Follow-up worth taking: with foreign reads on, much of the registries' readonly
getter and log-dumping surface (getDelegation, getPeriodSummary, logCommitteePages,
getEscrow, ...) exists only because cross-app box reads used to be impossible.
Not touched here.

Suite green: 539 passed (2 new).
Git Commit 104f0bc5 Branch feat/avm13-foreign-box-reads Document 22/6,588 ++ 6,035 --
tasosbit gGov
feat: take child approval bytecode in three pages
uploadPeriodApproval/uploadInstanceApproval now take page1/page2/page3, and the
two per-page length asserts are gone from both.

The asserts (page.length <= 4096, ERR:AP_LN) could never fire: the network
rejects any application argument over 4096 bytes before the program runs, so an
over-long page never reaches them. errApprovalPageTooLong goes with them -
nothing else raised it.

A third page raises what the ABI can carry from 8188 to 12282 bytes of program -
a page holds 4094, not 4096, because an ARC-4 byte[] spends 2 bytes on its
length prefix - which is the room an approval program needs once it grows into
v13's 7 extra program pages. Trailing pages may be empty; each non-empty page is
written at the running offset, so the split points still carry no meaning.

The SDK wrappers pass an empty page3 for now. Two ceilings bind before it can be
filled: createPeriod/createInstance read the approval box back as two 4096-byte
pages, and a single app call can only buy 8 box references - 8192 bytes of box
write budget - so a larger upload needs the write split across more app calls
first.

Ran: frac-delegation suite (246 passed), ggov-registry admin + periods (43
passed). Full suite not re-run.
Git Commit d9a4e21b Branch feat/avm13-foreign-box-reads Document 21/7,406 ++ 6,723 --