Ecosystem metrics
- New Repos
- 12
- New
- Commits
- 661
- down 11.2%
- Releases
- 1
- down 75.0%
- Contributors
- 43
- down 12.2%
- Merges
- 23
- down 8.0%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
7989 commits in all time
Jul 04, 2026 20:24 – Oct 02, 2026 20:24 UTC
Merge bfe26221024cd4be958c143788236b0c619de9f5 into 3874f81385d094c5974c5c2afff2af5a2c82b503
8d4defa5
pull/6752/merge
17/4,028 ++ 1,447 --
build: use workspace:^ for wallet adapters' core peer (#467)
The hardcoded "^5.0.0" peer range excludes prerelease versions, so installing prerelease adapters alongside prerelease core (e.g. 5.1.0-next.1 from the next channel) fails with ERESOLVE under npm. workspace:^ is rewritten at publish to ^<version>: ^5.1.0-next.1 for prereleases and ^5.1.0 for stable releases, matching how lockstep versioning ships them.
69e6af84
main
9/9 ++ 9 --
build: use workspace:^ for wallet adapters' core peer
The hardcoded "^5.0.0" peer range excludes prerelease versions, so installing prerelease adapters alongside prerelease core (e.g. 5.1.0-next.1 from the next channel) fails with ERESOLVE under npm. workspace:^ is rewritten at publish to ^<version>: ^5.1.0-next.1 for prereleases and ^5.1.0 for stable releases, matching how lockstep versioning ships them.
27e039ac
build/adapter-core-peer-range
9/9 ++ 9 --
ci: add next branch as a prerelease channel (#466)
Pushes to next publish prerelease versions (e.g. 5.1.0-next.N) to the next npm dist-tag, and CI runs on pull requests into next. publish-packages.mjs already tags prerelease versions as next, and Discord announcements already skip prereleases.
0052ac40
main
4/8 ++ 8 --
Merge d7fbc5c04c30fee068ab3e568158e5fb665fe693 into 4fe8544777cdc3ee549d67f90e90cc16374182ba
ceb885a9
pull/466/merge
4/8 ++ 8 --
ci: add next branch as a prerelease channel
Pushes to next publish prerelease versions (e.g. 5.1.0-next.N) to the next npm dist-tag, and CI runs on pull requests into next. publish-packages.mjs already tags prerelease versions as next, and Discord announcements already skip prereleases.
d7fbc5c0
ci/next-prerelease-channel
4/8 ++ 8 --
Merge 9663cd448fe4f064b92445a00ba0d3a916d5e927 into ba321bafca1d7ac0245d8e2aa972def9b686b763
6ed0f0e4
pull/406/merge
114/6,505 ++ 823 --
feat: add validator to explicitly exclude mismatching signature scenarios in inheritance chains
b6c4ead1
fix/override-divergence
4/111 ++ 1 --
test: various inheritance scenarios triggering the divergence
c17f0588
fix/override-divergence
3/209 ++ 0 --
Merge fe6f85ec81d3ca2f149b96b3ae94976cc0479d63 into 3874f81385d094c5974c5c2afff2af5a2c82b503
5e9a911c
pull/6753/merge
2/8 ++ 6 --
Merge f62f9516fa425b6d7aa02e6ad984d6bbce6da0de into 4fe8544777cdc3ee549d67f90e90cc16374182ba
e48b0c98
pull/465/merge
21/1,492 ++ 34 --
add Go Benchmark (go) benchmark result for 3874f81385d094c5974c5c2afff2af5a2c82b503
17464978
gh-pages
1/445 ++ 1 --
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&s=80)
Merge 01cfc9c72f2e2b11984e5353a08c653d79795c95 into 3874f81385d094c5974c5c2afff2af5a2c82b503
29de4ad1
pull/6755/merge
2/23 ++ 21 --
build(deps): bump go.opentelemetry.io/otel/sdk from 1.43.0 to 1.45.0
Bumps [go.opentelemetry.io/otel/sdk](https://github.com/open-telemetry/opentelemetry-go) from 1.43.0 to 1.45.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md) - [Commits](https://github.com/open-telemetry/opentelemetry-go/compare/v1.43.0...v1.45.0) --- updated-dependencies: - dependency-name: go.opentelemetry.io/otel/sdk dependency-version: 1.45.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
01cfc9c7
dependabot/go_modules/go.opentelemetry.io/otel/sdk-1.45.0
2/23 ++ 21 --
Merge 86035fab92e9254b36c1622a18a293022df7c63a into 3874f81385d094c5974c5c2afff2af5a2c82b503
df2e6130
pull/6746/merge
2/23 ++ 21 --
Merge d60b10a1aa2630d0309c9535356d797339289d4b into 3874f81385d094c5974c5c2afff2af5a2c82b503
0f7f9b46
pull/6742/merge
2/23 ++ 21 --
crypto: add Falcon-512 support alongside Falcon-1024 (#6703)
Co-authored-by: Pavel Zbitskiy <65323360+algorandskiy@users.noreply.github.com> Co-authored-by: Cosimo Bassi <65770425+cusma@users.noreply.github.com>
3874f813
master
51/2,825 ++ 960 --
feat: support post-quantum accounts with empty signatures
Wallets can advertise each account's empty signature (the signature fields of a SignedTransaction, base64 msgpack without `txn`) so dApps know the account type and can simulate with correctly-shaped signatures for fees. - WalletAccount.emptySignature, plus encode/decode/getSignatureType helpers - emptyTransactionSigner on wallets, the manager and all framework hooks - Manager checks empty signatures against algod's auth address on connect, resume and network change, and clears them when an account was rekeyed - signData throws for PQ accounts until ARC-60 supports them - WalletConnect reads empty signatures from scopedProperties on approval - Raise the algosdk peer floor to ^3.7.0 for pqsig support
f62f9516
feat/pq-empty-signatures
21/1,492 ++ 34 --
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4&s=80)
Merge 83b1a2dc381fe7822e3d2960fda88291eca1692b into 4fe8544777cdc3ee549d67f90e90cc16374182ba
fd1bca24
pull/460/merge
10/240 ++ 228 --
chore(deps): update non-major dependencies
83b1a2dc
renovate/non-major-dependencies
10/240 ++ 228 --
chore(deps): update dependency algosdk to v3.8.0 (#461)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
4fe85447
main
22/81 ++ 81 --
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&s=80)
Merge 397d47a7a1be1559774749695f0069d10e0b0436 into a93a3c04c1f147fbc3d9f582b814cd417de886a0
fe2f138b
pull/847/merge
1/13 ++ 0 --