Ecosystem metrics
- New Repos
- 1,879
- New
- Commits
- 58
- up 48.7%
- Releases
- 8
- up 33.3%
- Contributors
- 26
- up 18.2%
- Merges
- 2
- up 100.0%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
533 commits in all time
May 20, 2026 07:38 – Aug 18, 2026 07:38 UTC
Merge 0d42a5f7258852c30958e5d9644ab7962d2f24d3 into c1e451f3864d614d28a54c6e5beacd19cdb71592
fa5e8421
undefined
5/657 ++ 349 --
Merge 4b3bd37c1f13d8a1d5b98f57b1ccb3c9fb9c703e into c1e451f3864d614d28a54c6e5beacd19cdb71592
3ec779c2
pull/38/merge
2/144 ++ 1 --
Also verify the typed client, the artifact the tests actually run against
There are TWO arrows out of the committed artifact, not one, and neither was
checked:
contracts/out/TrelyanInscription.*
| algod compile | algokit generate client
v v
bytecode ==? chain contracts/trelyan_client.py
The client branch matters more than it looks. contracts/trelyan_client.py is an
89 KB generated file stamped "DO NOT MODIFY IT BY HAND", and the LocalNet suite
deploys the committed TEAL and drives it THROUGH that client. CI only ever
consumes it; nothing regenerated it and compared. A contract whose ABI moved
without the client being regenerated would be exercised by a suite talking to
the old interface -- and the suite would pass.
CHECKED WITHOUT RUNNING THE GENERATOR, DELIBERATELY
`algokit generate client` needs algokitgen-py, which would pin this check to a
generator version whose formatting churn is not a finding. It is also, on the
machine this was written on, blocked outright by a Windows Application Control
policy (os error 4551) -- the same policy that currently blocks cargo-deny.
No generator is needed: the client EMBEDS the full spec it was generated from,
in _APP_SPEC_JSON. Comparing that to the committed arc56.json needs nothing but
the two committed files, runs anywhere, and is stable across generator versions.
The comparison is on PARSED JSON rather than bytes, because the client embeds
the spec minified while arc56.json is pretty-printed -- a byte comparison would
fail always and therefore mean nothing.
Failure reporting distinguishes an ABI-method change (names differ; the suite is
testing a different interface) from a signature/struct/metadata change (names
agree), because those read very differently to a reviewer.
VERIFIED
- clean tree: all five artifacts plus the client in step, exit 0
- rename a method inside the client's embedded spec: CLIENT DRIFT, exit 1,
naming both method lists
- a missing _APP_SPEC_JSON block is reported as "repair the check", not
silently passed -- if the generator's output shape changes, this check stops
reading what it thinks it reads, and that is a finding about the check
ee6e17aa
ci/verify-teal-matches-source
1/87 ++ 4 --
Merge 0f0d14b1c9320f12d582efbed76476a2e838ea20 into b27decbb670d4d5e481699358da41e34ddfc26a4
8ac1dfbb
pull/592/merge
11/516 ++ 213 --
Merge 4cee93a5d9aa96a99d25a6d1288d01e6f0fdfac8 into 9bc334a8819e21a61e5717e04c07dec184a7c579
5523d1ef
pull/73/merge
2/205 ++ 329 --
Merge b60d7a6bbad5c6756581271bd035e01034cbb4cc into 0b42a140b8b4e7209c648f9c8dd5f9f0043e42ac
028df353
pull/637/merge
1/0 ++ 1 --
Merge 59fd5c909fce3e0c675b8ca6b090f58157105095 into fd2b3698ab3576338916b442e7dc1078c851955e
de33fd5e
pull/632/merge
3/57 ++ 11 --
Merge b175262b6f5bbfd406604d978d217ec991cbf566 into 8602e0430cdc499f3bc1cecc5abe4aa31f4aee44
13f0968a
pull/172/merge
85/9,658 ++ 8,186 --
Merge f131b95a4cea7f1657ab8c703caa09836cdae81c into 8602e0430cdc499f3bc1cecc5abe4aa31f4aee44
5ef057f9
pull/162/merge
142/15,514 ++ 7,959 --
chore: get rid of avm 13 exclusions now that localnet has v13
ab97d068
pull/744/head
1/0 ++ 12 --
ANGULAR: add Pulsechain to Trending Tokens
ed4806b9
master
4/52 ++ 11 --
cicd deploy stable 1.2026.08.13-stable [skip ci]
55c5e3eb
master
2/2 ++ 2 --