Ecosystem metrics

New Repos
24
New
Commits
586
up 13.3%
Releases
2
down 66.7%
Contributors
51
up 2.0%
Merges
14
up 7.7%

Repository Explorer

7422 commits in all time Jun 20, 2026 20:26 – Sep 18, 2026 20:26 UTC
scholtz BiatecWeb
cicd deploy
Git Commit 08c3708b Branch main Document 1/1 ++ 1 --
scholtz BiatecWeb
Refactor code structure for improved readability and maintainability
Git Commit a4fd8ee4 Branch main Document 2/46 ++ 1 --
d13co reti
Merge 35981bfe47383e17ee86b1ce49495d9d9be3165f into bdb51c26c3f8c5b9a5ebad9fe8947063f4c4feec
Git Commit 243dffd4 Branch pull/413/merge Document 2/23 ++ 21 --
d13co reti
merge dev, resolve pnpm-lock.yaml conflict
Git Commit 35981bfe Branch pull/413/head Document 58/3,161 ++ 531 --
algorandskiy go-algorand
Merge f4c1612e0bbc511c840f8dda419c17c0041cc08d into 8cd5eb5f667c01ca6812e4d2f82930a793e23b18
Git Commit e29f3b36 Branch pull/6744/merge Document 3/144 ++ 2 --
algorandskiy go-algorand
p2p: track handleConnected termination
Git Commit f4c1612e Branch pull/6744/head Document 3/144 ++ 2 --
d13co reti
fix: bump algokit-utils to 9.2.2, fixes PQ txn confirmations
Git Commit 65b3dcc3 Branch pull/413/head Document 2/23 ++ 7 --
algorandskiy go-algorand
Merge 505e75762087072c03e7319cdff10f449353f3b3 into 8cd5eb5f667c01ca6812e4d2f82930a793e23b18
Git Commit f1a3d580 Branch pull/6743/merge Document 23/3,378 ++ 249 --
Merge 74d436e0a252e6fc0451209b9bb48826ec8bbb15 into 361d3066ffaca4241991cc6563403417bf562ecf
Git Commit 7e588487 Branch pull/17/merge Document 4/3,363 ++ 1,957 --
fix(deps): update all non-major dependencies
Git Commit 74d436e0 Branch renovate/all-minor-patch Document 4/3,363 ++ 1,957 --
experimental: for review and consolidation with pera
Git Commit 68aed235 Branch experimental/use-wallet-e2e Document 300/60,952 ++ 4,342 --
Merge 8ea967614ccef5a3f64a861d1d6a2e8c10a01d94 into dd1fed50cdc18a699a994b25a1d4bdb11b902553
Git Commit 2dc9f2c0 Branch pull/71/merge Document 4/73 ++ 0 --
fix(utils): validate sender address in sign_with_private_key and signed_transactions in submit
Git Commit 8ea96761 Branch pull/71/head Document 4/73 ++ 0 --
cce go-algorand
Merge 4884700e237d5fd32124be7da14dc16d445c7460 into 8cd5eb5f667c01ca6812e4d2f82930a793e23b18
Git Commit faf06f15 Branch pull/6740/merge Document 10/396 ++ 78 --
cce go-algorand
ci: merge every partition's coverage before uploading it
Each partition uploaded its own report and left Codecov to combine them,
which had two problems. A partition that failed still let the other five
report, so a run that lost a sixth of its tests produced a quietly lower
number rather than no number. And with -coverpkg every partition's
profile carries the whole block set, mostly zeroed, so combining them
meant relying on Codecov's merge -- the same merge that mishandles
duplicate blocks within a file.

Have each partition keep its raw coverage data as an artifact and add one
job that merges all of them with "go tool covdata" and uploads a single
report. Needing the test job is what makes this safe: a job runs only
once every leg of the matrix it needs has succeeded, so a failed
partition means no upload at all rather than a report missing part of the
run, and nothing about the result depends on how Codecov combines
reports.

For the nightly that also means a failure on macos or arm holds back the
baseline for that commit, since they share one matrix with the platform
that measures coverage. Codecov walks back to the nearest ancestor that
has a report, so a gap costs a comparison against a slightly older base
rather than a missing one.

Verified that the merge reconstructs a partitioned run: over config,
util/metrics and data/bookkeeping, partition 0 alone covers 15.6% and
partition 1 alone 23.0%, while the two merged give 25.8%, exactly the
unpartitioned figure.

merge_coverage.sh now takes the output first and any number of coverage
data directories after it. Drop comment.after_n_builds with the extra
uploads: there is one report per commit now, so there is nothing to wait
for, and the setting would have meant a comment never appearing at all if
one upload went missing.
Git Commit 4884700e Branch pull/6740/head Document 6/98 ++ 44 --
cce go-algorand
ci: merge every partition's coverage before uploading it
Each partition uploaded its own report and left Codecov to combine them,
which had two problems. A partition that failed still let the other five
report, so a run that lost a sixth of its tests produced a quietly lower
number rather than no number. And with -coverpkg every partition's
profile carries the whole block set, mostly zeroed, so combining them
meant relying on Codecov's merge -- the same merge that mishandles
duplicate blocks within a file.

Have each partition keep its raw coverage data as an artifact and add one
job that merges all of them with "go tool covdata" and uploads a single
report. Needing the test job is what makes this safe: a job runs only
once every leg of the matrix it needs has succeeded, so a failed
partition means no upload at all rather than a report missing part of the
run, and nothing about the result depends on how Codecov combines
reports.

For the nightly that also means a failure on macos or arm holds back the
baseline for that commit, since they share one matrix with the platform
that measures coverage. Codecov walks back to the nearest ancestor that
has a report, so a gap costs a comparison against a slightly older base
rather than a missing one.

Verified that the merge reconstructs a partitioned run: over config,
util/metrics and data/bookkeeping, partition 0 alone covers 15.6% and
partition 1 alone 23.0%, while the two merged give 25.8%, exactly the
unpartitioned figure.

merge_coverage.sh now takes the output first and any number of coverage
data directories after it. Drop comment.after_n_builds with the extra
uploads: there is one report per commit now, so there is nothing to wait
for, and the setting would have meant a comment never appearing at all if
one upload went missing.
Git Commit 76f55302 Branch pull/6740/head Document 6/97 ++ 43 --
cce go-algorand
codecov: leave components out for now
Component ids are immutable once used, so the split is worth settling
deliberately rather than guessing at it here. There is also nothing yet
worth measuring them against: every report Codecov currently holds is
either partial-coverage or scrambled by the duplicate-block bug, and
component analytics backfill over whatever history exists.

Adding them later costs nothing -- they are defined entirely in this file
and need no change to the uploads -- and by then people will have been
reading the new comments and can say what split they actually want.
Git Commit 22b15ab5 Branch pull/6740/head Document 1/1 ++ 16 --
onetechnical go-algorand
Merge 89d41a93a30acecdac038adf842653d3f5ef7fb7 into 8cd5eb5f667c01ca6812e4d2f82930a793e23b18
Git Commit 2a1729b5 Branch pull/6567/merge Document 16/1,647 ++ 22 --
onetechnical go-algorand
Update comment about version being same or newer
Git Commit 1498cc81 Branch pull/6567/head Document 1/1 ++ 1 --
onetechnical go-algorand
Zip windows binaries into a bin/ subdirectory
Git Commit c5ca10f0 Branch pull/6567/head Document 1/5 ++ 2 --
onetechnical go-algorand
Update comment to reflect expansion to MSYS
Git Commit fefea08c Branch pull/6567/head Document 1/3 ++ 1 --
onetechnical go-algorand
Skip node exporter on Windows, which is just a stub anyway
Git Commit 53b77e27 Branch pull/6567/head Document 3/17 ++ 11 --
onetechnical go-algorand
Address criticism of setting owner/group in potentially undefined context
Git Commit 92097bb5 Branch pull/6567/head Document 1/0 ++ 2 --