Ecosystem metrics
- New Repos
- 25
- New
- Commits
- 674
- up 16.0%
- Releases
- 1
- down 83.3%
- Contributors
- 49
- down 16.9%
- Merges
- 7
- down 69.6%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
7382 commits in all time
Jun 24, 2026 19:33 – Sep 22, 2026 19:33 UTC
provider canary hardening [step 1] Enforce provider type assertions in CI
Co-authored-by: Junie <junie@jetbrains.com>
bf92347d
discussion/namespaces-overrides
4/34 ++ 6 --
provider canary hardening [step 1] Harden package contents and provider option typing
Co-authored-by: Junie <junie@jetbrains.com>
fe109bb0
discussion/namespaces-overrides
5/80 ++ 6 --
Add a portable KAT format, and a tool to produce and check it
The committed KAT arrays derive each key from a seeded PRNG, which no other implementation can reproduce. tests/kat_tool re-exports the same vectors with keys, public keys and messages as literal bytes, so a port in another language needs only a signer. make kat regenerate the committed files make check-kat re-derive every record and compare (added to CI) make kat-full write the exhaustive 512-record sets See kat/README.md for the format.
e753f8d4
pull/18/head
7/1,640 ++ 2 --
Merge 27d304e0a36633966d1986ad54247146bbc9e3a9 into 7fdd08948797fd0e5517f8e7ed0ec0ed65d7fa22
f837dd58
pull/6/merge
2/53 ++ 1 --
chore: include dependabot configs
27d304e0
chore/dependabot-updates
2/53 ++ 1 --
Merge 69050a307f7866a2e0f62b5dacec2d4a68ffc55f into 3840d6f5e8c73e27141c5752d311c54c2efcf892
fb74b41e
pull/37/merge
3/63 ++ 1 --
chore: include dependabot configs
69050a30
chore/dependabot-updates
3/63 ++ 1 --
Merge 399f42e843f89c8b55fc335f58f8f8d69981c24c into 515a25aa1cbe1d69b4c4c6e60dcd2143613ef83e
ddbcf456
pull/6707/merge
17/2,342 ++ 60 --
Merge 01ad2e0a03d0f6935a732397654025462e08b597 into 515a25aa1cbe1d69b4c4c6e60dcd2143613ef83e
3428f1a2
pull/6730/merge
1/3 ++ 3 --
Merge b7b57cbbc63fb821081952170ebdd5bb4f9d6bab into 45d268b61c56dddf32976fdff5832b78bacd221c
082bdd4d
pull/178/merge
7/76 ++ 5 --
Merge 8401ac78d9272865345a33c229c211611ade765b into 515a25aa1cbe1d69b4c4c6e60dcd2143613ef83e
6ed9c57d
pull/6733/merge
2/40 ++ 25 --
Merge b6e36d117a6e3f005b6b4061d73fef98b07ea0f1 into 515a25aa1cbe1d69b4c4c6e60dcd2143613ef83e
c33e873a
pull/6735/merge
16/650 ++ 504 --
feat: support algosdk 3.8 v41/42 block header fields (prev512, txn512, ld, ct)
b7b57cbb
feat/block-header-v41-v42
7/76 ++ 5 --
Merge 8c3ec7a61949411bcd3c870f548a553ca83d1584 into c91d55b8c1a3b364b3cf61c52972ca549682377f
dcfb57d6
pull/825/merge
52/2,985 ++ 600 --
feat: use pointers for signer equality check
This more closely matches the behavior of JS and Py. The idea is that one address could have multiple signers, although I'm not sure how common that actually is. This definitely feels more correct, but if there are downsides I'm not seeing we could revert it
8c3ec7a6
pqsig-support
9/74 ++ 42 --
Merge 7c2d5faed3d93393d591798d0b2fe4a667c22ff7 into 118ac25c1e5a8b4c3fc53f0bc79db34edb90d92a
fa256dfa
pull/1139/merge
1/7 ++ 4 --