Ecosystem metrics

New Repos
20
down 98.9%
Commits
848
down 18.9%
Releases
4
down 55.6%
Contributors
36
down 34.5%
Merges
35
up 2.9%

Repository Explorer

6912 commits in all time Jun 02, 2026 12:41 – Aug 31, 2026 12:41 UTC
dependabot[bot] algonaut
Merge b5ecd288d61efc2d7096147e61e2eb501de39446 into 65c365bfc61c2c732baadc815f4578893c932833
Git Commit 0b6631bf Branch pull/381/merge Document 1/1 ++ 1 --
dependabot[bot] algonaut
chore(deps): update jsonschema requirement from 0.46 to 0.52
Updates the requirements on [jsonschema](https://github.com/Stranger6667/jsonschema) to permit the latest version.
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](https://github.com/Stranger6667/jsonschema/compare/cli-v0.46.0...cli-v0.52.0)

---
updated-dependencies:
- dependency-name: jsonschema
  dependency-version: 0.52.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Git Commit b5ecd288 Branch dependabot/cargo/jsonschema-0.52 Document 1/1 ++ 1 --
joe-p indexer
Merge bfda25a76f939fc31387cd07ceb84426319c2e63 into f84ad3e337a2e6eb111ac548f21dc65df8cc5e70
Git Commit 709c30f5 Branch pull/1699/merge Document 10/676 ++ 461 --
ipaleka frontend
Bugfix for not working auto-refresh in the Dynamic layout
Git Commit 2e2dba4e Branch v1_0_0 Document 5/134 ++ 6 --
ipaleka frontend
Bugfix for not working auto-refresh in the Dynamic layout
Git Commit cdd2d5bd Branch v1_0_0 Document 4/116 ++ 5 --
gabrielkuettel devportal
Merge 71cf7569c529ad182f6af772d273649d0accff71 into 623f3c058154e12632360cbd84a2d3c0c078314e
Git Commit 78decb65 Branch pull/653/merge Document 7/15,608 ++ 7 --
ipaleka frontend
All the Jest HTML fixtures are updated to reflect new design
Git Commit 77b24d69 Branch v1_0_0 Document 12/853 ++ 354 --
gabrielkuettel devportal
Merge 46e189ff835943520445eb46c6cbda7b0135b97a into 623f3c058154e12632360cbd84a2d3c0c078314e
Git Commit 80e6e15f Branch pull/613/merge Document 3/4,193 ++ 0 --
dependabot[bot] devportal
Merge 8b6d50495e60448509422fe59f56c1cfd8406410 into 623f3c058154e12632360cbd84a2d3c0c078314e
Git Commit 623933fa Branch pull/586/merge Document 2/8 ++ 7 --
manuelmauro algonaut
docs(readme): add a compatibility matrix and acceptance-suite coverage (#380)
* fix(crypto): drop redundant reference in Signature's Debug impl

clippy 1.97 promotes `useless_borrows_in_formatting` to fire on
`write!(f, "{}", &BASE64.encode(..))`. CI pins `rust-toolchain@stable`,
so this fails the clippy job as runners pick up the new release, and it
already fails the pre-commit hook locally.

* docs(readme): add a compatibility matrix and acceptance-suite coverage

The README documented what algonaut does but never stated how it compares
to the reference SDK or what it is verified against, so a reader had no way
to judge coverage or find the gaps without reading the source.

Add a Compatibility section with two reference points:

- The cross-SDK algorand-sdk-testing acceptance suite: per-feature status
  for all 30 upstream features (13/13 integration, 5/17 unit), the 274/0
  fresh-harness result, and the rationale behind every skipped scenario.
- js-algorand-sdk v3.7.0: a surface-by-surface capability matrix across
  clients, transactions, signing, groups/ABI, and tooling.

Gaps are stated explicitly rather than omitted — algod 5.0 / Falcon-1024
post-quantum accounts and resource access lists, TEAL signing, ufixedNxM
and anonymous tuples in contract! (#345), the 12 unit features awaiting
step definitions, and the lack of a pluggable HTTP transport.

* fix(cucumber): drop the dryrun features removed upstream

algorand-sdk-testing removed dryrun.feature, dryrun_testing.feature and
dryrun_trace.feature in algorand/algorand-sdk-testing#325 (2026-07-14).
test.env tracks that repo, so a fresh CI clone no longer ships those files
while the runner still listed the first two as live. cucumber reported two
parsing errors and the suite exited 1 — on a docs-only branch, a month
after the upstream change landed.

Drop all three Feature entries, along with the step definitions they were
the only callers of: the integration dryrun module, the World's
dryrun_response and dryrun_kind fields, the two unit dryrun steps (upstream
stripped dryrun from v2algodclient_responses.feature in the same commit),
and UnitResponse::Dryrun. Every step phrase involved was exclusive to the
deleted features.

The SDK's dryrun support is untouched: algonaut::dryrun, algod.teal_dryrun,
the models and the trace printer all ship, covered by the unit tests in
src/dryrun.rs. What is gone is the live-node coverage, and that went when
upstream deleted the fixtures.

* ci(cucumber): pin the test harness to a commit

test.env tracked algorand-sdk-testing's master, so any upstream edit to the
shared feature files landed as a red build on whatever unrelated PR ran
next. The dryrun removal in algorand/algorand-sdk-testing#325 broke a
docs-only branch a month after it was merged, with nothing in this repo
having changed.

Pin SDK_TESTING_BRANCH to 0fbe354f, the tree the suite was last verified
green against. algorand-sdk-testing publishes no tags or releases, so a
commit SHA is the only stable ref available.

`git clone --branch` accepts a branch or tag but not a SHA, so fetch the ref
explicitly instead. The fetch stays shallow and resolves all three kinds of
ref, so SDK_TESTING_BRANCH=master still works for testing against upstream
tip. The script now logs which ref it resolved.

* docs(readme): refresh acceptance-suite counts after the dryrun removal

The compatibility matrix was measured against the pre-removal harness. With
dryrun.feature, dryrun_testing.feature and dryrun_trace.feature gone
upstream, the suite is 11/11 integration and 5/16 unit across 27 features,
and a fresh harness reports 249 scenarios passed, 0 failed (265 collected,
16 excluded).

Verified twice against the now-pinned harness at 0fbe354f, both runs
identical. The 227 offline-test figure is unchanged.

* docs(readme): correct the simulate exclusion causes and unit counts

Two review findings on the compatibility matrix, both pre-existing in the
section as first written.

The three simulate exclusions were all attributed to the group builder's
allow-empty-signatures behaviour, but tests/cucumber/main.rs assigns them
three separate causes: allow-empty-signatures covers only "Simulating
unsigned transactions in the ATC group", exec_trace_with_stack_scratch is
the ATC base64-decode issue in #266, and exec_trace_with_state_change_and_hash
needs a create-and-optin on-complete combo. Misattributing them undercuts
the section's claim that every exclusion names a concrete gap.

The unit row read "11 await step definitions, not SDK capability", which is
false for tealsign — the table marks it ❌ for a capability gap, not ⏳.
Split the count: 10 need only step definitions, tealsign also needs the
capability. The 11 total is kept in the gaps list, since that bullet counts
features that are not live rather than features blocked on step definitions
alone.

The simulate causes stay inside footnote 2; the list is keyed to the ¹-⁵
superscripts in the tables above, so a new item would misalign them.
Git Commit 65c365bf Branch main Document 11/195 ++ 411 --
manuelmauro algonaut
docs(readme): correct the simulate exclusion causes and unit counts
Two review findings on the compatibility matrix, both pre-existing in the
section as first written.

The three simulate exclusions were all attributed to the group builder's
allow-empty-signatures behaviour, but tests/cucumber/main.rs assigns them
three separate causes: allow-empty-signatures covers only "Simulating
unsigned transactions in the ATC group", exec_trace_with_stack_scratch is
the ATC base64-decode issue in #266, and exec_trace_with_state_change_and_hash
needs a create-and-optin on-complete combo. Misattributing them undercuts
the section's claim that every exclusion names a concrete gap.

The unit row read "11 await step definitions, not SDK capability", which is
false for tealsign — the table marks it ❌ for a capability gap, not ⏳.
Split the count: 10 need only step definitions, tealsign also needs the
capability. The 11 total is kept in the gaps list, since that bullet counts
features that are not live rather than features blocked on step definitions
alone.

The simulate causes stay inside footnote 2; the list is keyed to the ¹-⁵
superscripts in the tables above, so a new item would misalign them.
Git Commit 93ea2d79 Branch pull/380/head Document 1/12 ++ 7 --
ipaleka frontend
All the Jest HTML fixtures are updated to reflect new design
Git Commit 6ea37072 Branch v1_0_0 Document 9/750 ++ 349 --
Ganainmtech devportal
Merge 623f3c058154e12632360cbd84a2d3c0c078314e into 4cb7c04a029540b737f7ae354db5e823101fdaf1
Git Commit bbe1ac36 Branch pull/659/merge Document 3/29 ++ 2 --
manuelmauro algonaut
Merge c6512a0bc63bc85dd6c0bab6e5023f7d658bf8c1 into 4144110e83b9afe1570a9e602f4a520dc997c6b7
Git Commit 06d0834a Branch pull/380/merge Document 11/190 ++ 411 --
Ganainmtech devportal
Merge pull request #658 from algorandfoundation/feat/social-meta-tags
feat: add Twitter/X meta tags and fix og:image URL
Git Commit 623f3c05 Branch main Document 3/29 ++ 2 --
manuelmauro algonaut
docs(readme): refresh acceptance-suite counts after the dryrun removal
The compatibility matrix was measured against the pre-removal harness. With
dryrun.feature, dryrun_testing.feature and dryrun_trace.feature gone
upstream, the suite is 11/11 integration and 5/16 unit across 27 features,
and a fresh harness reports 249 scenarios passed, 0 failed (265 collected,
16 excluded).

Verified twice against the now-pinned harness at 0fbe354f, both runs
identical. The 227 offline-test figure is unchanged.
Git Commit c6512a0b Branch docs/compatibility-matrix Document 1/15 ++ 16 --
manuelmauro algonaut
ci(cucumber): pin the test harness to a commit
test.env tracked algorand-sdk-testing's master, so any upstream edit to the
shared feature files landed as a red build on whatever unrelated PR ran
next. The dryrun removal in algorand/algorand-sdk-testing#325 broke a
docs-only branch a month after it was merged, with nothing in this repo
having changed.

Pin SDK_TESTING_BRANCH to 0fbe354f, the tree the suite was last verified
green against. algorand-sdk-testing publishes no tags or releases, so a
commit SHA is the only stable ref available.

`git clone --branch` accepts a branch or tag but not a SHA, so fetch the ref
explicitly instead. The fetch stays shallow and resolves all three kinds of
ref, so SDK_TESTING_BRANCH=master still works for testing against upstream
tip. The script now logs which ref it resolved.
Git Commit 3e93abf6 Branch docs/compatibility-matrix Document 2/17 ++ 3 --
manuelmauro algonaut
fix(cucumber): drop the dryrun features removed upstream
algorand-sdk-testing removed dryrun.feature, dryrun_testing.feature and
dryrun_trace.feature in algorand/algorand-sdk-testing#325 (2026-07-14).
test.env tracks that repo, so a fresh CI clone no longer ships those files
while the runner still listed the first two as live. cucumber reported two
parsing errors and the suite exited 1 — on a docs-only branch, a month
after the upstream change landed.

Drop all three Feature entries, along with the step definitions they were
the only callers of: the integration dryrun module, the World's
dryrun_response and dryrun_kind fields, the two unit dryrun steps (upstream
stripped dryrun from v2algodclient_responses.feature in the same commit),
and UnitResponse::Dryrun. Every step phrase involved was exclusive to the
deleted features.

The SDK's dryrun support is untouched: algonaut::dryrun, algod.teal_dryrun,
the models and the trace printer all ship, covered by the unit tests in
src/dryrun.rs. What is gone is the live-node coverage, and that went when
upstream deleted the fixtures.
Git Commit 22c4973e Branch docs/compatibility-matrix Document 7/9 ++ 406 --
ipaleka widgets
Historic widget's Jest fixture is updated
Git Commit 74ab11fa Branch main Document 7/731 ++ 195 --
manuelmauro algonaut
Merge e104414f413859369705256ab846c146a8454ee7 into 4144110e83b9afe1570a9e602f4a520dc997c6b7
Git Commit c2379948 Branch pull/380/merge Document 2/165 ++ 2 --
manuelmauro algonaut
docs(readme): add a compatibility matrix and acceptance-suite coverage
The README documented what algonaut does but never stated how it compares
to the reference SDK or what it is verified against, so a reader had no way
to judge coverage or find the gaps without reading the source.

Add a Compatibility section with two reference points:

- The cross-SDK algorand-sdk-testing acceptance suite: per-feature status
  for all 30 upstream features (13/13 integration, 5/17 unit), the 274/0
  fresh-harness result, and the rationale behind every skipped scenario.
- js-algorand-sdk v3.7.0: a surface-by-surface capability matrix across
  clients, transactions, signing, groups/ABI, and tooling.

Gaps are stated explicitly rather than omitted — algod 5.0 / Falcon-1024
post-quantum accounts and resource access lists, TEAL signing, ufixedNxM
and anonymous tuples in contract! (#345), the 12 unit features awaiting
step definitions, and the lack of a pluggable HTTP transport.
Git Commit e104414f Branch docs/compatibility-matrix Document 1/164 ++ 1 --
manuelmauro algonaut
fix(crypto): drop redundant reference in Signature's Debug impl
clippy 1.97 promotes `useless_borrows_in_formatting` to fire on
`write!(f, "{}", &BASE64.encode(..))`. CI pins `rust-toolchain@stable`,
so this fails the clippy job as runners pick up the new release, and it
already fails the pre-commit hook locally.
Git Commit 634c4c96 Branch docs/compatibility-matrix Document 1/1 ++ 1 --
ipaleka frontend
When Moon button is retired
Git Commit 5acd9e1a Branch v1_0_0 Document 8/22 ++ 23 --
renovate[bot] use-wallet
Merge 07c5f60025f9c77b6b2d3d2b3c059788413d6331 into 7861a68efdc034d4a01f5ba68f1acff97e28e8e6
Git Commit 716fdbbc Branch pull/455/merge Document 3/3 ++ 3 --