Ecosystem metrics
- New Repos
- 26
- down 98.6%
- Commits
- 830
- down 22.5%
- Releases
- 4
- down 50.0%
- Contributors
- 36
- down 33.3%
- Merges
- 29
- down 27.5%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
6920 commits in all time
Jun 02, 2026 14:40 – Aug 31, 2026 14:40 UTC
Merge 8a3bb808d5b12e229f403c447f1d2f4d30211e5b into 7861a68efdc034d4a01f5ba68f1acff97e28e8e6
a532de4e
pull/450/merge
11/736 ++ 187 --
chore(deps): update wallet adapter packages
8a3bb808
renovate/wallet-adapter-packages
11/736 ++ 187 --
Merge 111c650464089ffc30741d54232345c9bc141ff9 into 65c365bfc61c2c732baadc815f4578893c932833
7def8b68
pull/374/merge
1/1 ++ 1 --
chore(deps): update ed25519-dalek requirement from 2.2.0 to 3.0.0
Updates the requirements on [ed25519-dalek](https://github.com/dalek-cryptography/curve25519-dalek) to permit the latest version. - [Release notes](https://github.com/dalek-cryptography/curve25519-dalek/releases) - [Changelog](https://github.com/dalek-cryptography/curve25519-dalek/blob/3.0.0/CHANGELOG.md) - [Commits](https://github.com/dalek-cryptography/curve25519-dalek/commits/3.0.0) --- updated-dependencies: - dependency-name: ed25519-dalek dependency-version: 3.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
111c6504
dependabot/cargo/ed25519-dalek-3.0.0
1/1 ++ 1 --
Merge e0f1f64e92213809889939c2d7f05ed7900612d6 into 65c365bfc61c2c732baadc815f4578893c932833
1c8d02a8
pull/375/merge
1/1 ++ 1 --
chore(deps): update syn requirement from 2.0 to 3.0
Updates the requirements on [syn](https://github.com/dtolnay/syn) to permit the latest version. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/2.0.0...3.0.2) --- updated-dependencies: - dependency-name: syn dependency-version: 3.0.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
e0f1f64e
dependabot/cargo/syn-3.0
1/1 ++ 1 --
Merge 262e430eaaa97ddfa1b3ab771b2a5d000da5bc3d into 65c365bfc61c2c732baadc815f4578893c932833
bc957c8c
pull/378/merge
1/1 ++ 1 --
chore(deps): update base64 requirement from 0.22 to 0.23
Updates the requirements on [base64](https://github.com/marshallpierce/rust-base64) to permit the latest version. - [Changelog](https://github.com/marshallpierce/rust-base64/blob/master/RELEASE-NOTES.md) - [Commits](https://github.com/marshallpierce/rust-base64/compare/v0.22.0...v0.23.0) --- updated-dependencies: - dependency-name: base64 dependency-version: 0.23.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
262e430e
dependabot/cargo/base64-0.23
1/1 ++ 1 --
Merge 922bb87799ddc8c4a123b7657e2231dd44ef9f61 into 65c365bfc61c2c732baadc815f4578893c932833
7e41b12e
pull/378/merge
1/1 ++ 1 --
Merge 222a2e5eaadb782f8471d2efd9059db93b2122b2 into 65c365bfc61c2c732baadc815f4578893c932833
7e8a8af3
pull/375/merge
1/1 ++ 1 --
Merge bb440a29ea64815b673e5d611baec2f8a9bb6b1c into 65c365bfc61c2c732baadc815f4578893c932833
8ee156d0
pull/374/merge
1/1 ++ 1 --
Merge d90a4ffaaecdf565ba0af27ebf608d83fb2abd39 into 65c365bfc61c2c732baadc815f4578893c932833
5da0c739
pull/372/merge
1/1 ++ 1 --
Merge f078c6da4fe77a7b6a498ef66d4416740dc70977 into 65c365bfc61c2c732baadc815f4578893c932833
2828daa3
pull/371/merge
1/1 ++ 1 --
Merge 53b7fe7f3ee681019faeadcbd24211a1a7aeecb6 into 65c365bfc61c2c732baadc815f4578893c932833
604cf592
pull/370/merge
1/1 ++ 1 --
Merge b5ecd288d61efc2d7096147e61e2eb501de39446 into 65c365bfc61c2c732baadc815f4578893c932833
0b6631bf
pull/381/merge
1/1 ++ 1 --
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>
b5ecd288
dependabot/cargo/jsonschema-0.52
1/1 ++ 1 --
Merge 71cf7569c529ad182f6af772d273649d0accff71 into 623f3c058154e12632360cbd84a2d3c0c078314e
78decb65
pull/653/merge
7/15,608 ++ 7 --
Merge 46e189ff835943520445eb46c6cbda7b0135b97a into 623f3c058154e12632360cbd84a2d3c0c078314e
80e6e15f
pull/613/merge
3/4,193 ++ 0 --
Merge 8b6d50495e60448509422fe59f56c1cfd8406410 into 623f3c058154e12632360cbd84a2d3c0c078314e
623933fa
pull/586/merge
2/8 ++ 7 --
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.
65c365bf
main
11/195 ++ 411 --
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.
93ea2d79
pull/380/head
1/12 ++ 7 --