Ecosystem metrics
- New Repos
- 26
- New
- Commits
- 518
- down 38.5%
- Releases
- 5
- down 16.7%
- Contributors
- 43
- down 4.4%
- Merges
- 6
- down 85.4%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
7089 commits in all time
Jun 10, 2026 22:12 – Sep 08, 2026 22:12 UTC
Merge 17af07d7dc133856d8f5733097a02e3c140ceea6 into cf3c69ab1f669a6554e13411a86d71757f8e2170
88120ec7
pull/6727/merge
7/34 ++ 34 --
refactor: switch to simulate for getSessionDyanmicData (#405)
243ec8e4
main
9/392 ++ 149 --
Merge 7ed4ef6757438792cfe11a4e299e10f0ea1daf2b into cf3c69ab1f669a6554e13411a86d71757f8e2170
eeaaa03c
pull/6727/merge
6/31 ++ 34 --
Merge a0546cc99eb1512877489c0cff1264a819b69f79 into 35d7e65be978b14e1777fb37c4a70fa92fe8022e
20c21f15
pull/12/merge
38/1,563 ++ 1,570 --
tests: fix flaky balance check in e2e-subs app-account
907c5a81
pull/6727/head
4/16 ++ 29 --
fix limit-swap-test.s
fix limit-swap-test.sh test
760469e2
pull/6727/head
1/5 ++ 3 --
Fix x402 skills: canonical @x402 facilitator API, CAIP-2 constants, route typing
a0546cc9
x402-skills-fixes
38/1,563 ++ 1,570 --
Merge f39f3dc4f2a28ffafa5dd22000db124fdc5ee746 into 35e28988cb6ac269cf322231075b00dbab656a95
8f265ca7
pull/405/merge
9/392 ++ 149 --
Merge 8c1d96b381268a1cb3bf1385e026874b0785c2dd into 4b7d97f1d58fcf3f3719dcff9be1ec2ea700fa63
4eed48f3
pull/209/merge
9/473 ++ 14 --
feat: resolve the ARC-60 signer for rekeyed accounts [PERA-4977]
8c1d96b3
yasincaliskan/arc60-resolve-signer
9/473 ++ 14 --
Merge bb884615cb88b114172a39521d12ffcc530a1095 into ec6c593a804c81f661cf4c003f17ff964d9cae95
5dd378d4
pull/36/merge
21/2,422 ++ 22 --
docs: add sequence diagram for credential status check and revocation process
bb884615
feat/credentials-status-and-revoke
1/21 ++ 0 --
Merge da85ec9b58bdbe6a0dab32676de3e352bce584ee into 623f3c058154e12632360cbd84a2d3c0c078314e
0e120734
pull/662/merge
7/28 ++ 11 --
docs: point Puya bulletin readers at the supported languages
da85ec9b
fix/pyteal-beaker-deprecation
1/2 ++ 0 --
Publish workflow: use default GITHUB_TOKEN for checkout, drop unused … (#1194)
* Publish workflow: use default GITHUB_TOKEN for checkout, drop unused PAT_GITHUB_ADMIN. * nx:fix: skip when nothing was built (workflow-only changes leave no dist/packages).
bbfbdf8c
v2
2/5 ++ 3 --
nx:fix: skip when nothing was built (workflow-only changes leave no dist/packages).
fa877083
pull/1194/head
1/5 ++ 0 --
Publish workflow: use default GITHUB_TOKEN for checkout, drop unused PAT_GITHUB_ADMIN.
fed42235
pull/1194/head
1/0 ++ 3 --
Merge 25b4299c4a61d7ea5aae54f99d727432ab4e50a4 into ec6c593a804c81f661cf4c003f17ff964d9cae95
4f75898e
pull/40/merge
27/2,483 ++ 53 --
docs: state the deprecated language guidance on the language pages
e64fa79d
fix/pyteal-beaker-deprecation
3/10 ++ 2 --
docs: record the algosdk pqsig blocker in the PQ accounts plan
Bring the plan in line with what increments 1 and 3 actually shipped, and settle the increment 4 design against the published SDKs. algokit-utils cannot emit a pqsig envelope in any released version - checked through 10.0.0-beta.4, the newest on npm - so increment 4 cannot be written against the packages currently installed. algosdk 3.7.0 has the full feature: SignedTransaction.pqsig, EncodedPQSig, addressFromPQKey/addressFromPQSig, an async remote-signer adapter shaped like a Vault call, and an empty-signature signer that makes algod report the real post-quantum fee under simulate. Adding algosdk 3.7.0 is therefore a hard prerequisite for increment 4, scoped to the PQ envelope and address helpers only; transaction building, grouping and encoding stay on algokit-utils. That supersedes the earlier plan to hand-assemble the envelope and promote algorand-msgpack to a direct dependency - hand-rolling canonical msgpack on a money path is the wrong trade when the SDK's own schema encoder is available. The two SDKs interoperate at the byte level, verified against the real packages: algosdk decodes algokit's encoded transaction (TX prefix stripped) and re-encodes it byte-identically, its bytesToSign output matches algokit's encodeTransaction exactly, an ed25519 signed transaction encodes identically under both, and the PQ address helpers agree with the Vault plugin's derivation. The rest tracks reality: increment 4 is no longer blocked on an unavailable algod version now that v5 is released, the increment 1 notes describe the plugin version pinning and mount verification that were built, account_type is required rather than optional, the signing call sites still discard the resolved UserAccount, and the review findings increment 4 has to clear are listed explicitly alongside the non-atomic cross-mount check left for cleanup.
25b4299c
feat/pq-accounts
1/143 ++ 44 --