Ecosystem metrics
- New Repos
- 12
- New
- Commits
- 666
- down 10.6%
- Releases
- 1
- down 75.0%
- Contributors
- 43
- down 12.2%
- Merges
- 24
- down 4.0%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
8008 commits in all time
Jul 04, 2026 23:32 – Oct 02, 2026 23:32 UTC
Merge 8722aa55e64c97d2b03bb745fb6619eedcf73927 into a8cffe939423a17871f2df8542c5253d3c148302
b2adf9de
pull/47/merge
4/240 ++ 56 --
fix: documentation to reflect resolved merge conflicts
8722aa55
fix/vault-namespace-header
2/2 ++ 2 --
Merge 40e8abbd731ae7139fb7c4bbf2ae058c70fc6c7d into 69e6af844b1ecb5787a45f132cce29daaac1cccf
139f74b0
pull/431/merge
16/1,099 ++ 122 --
feat: add SimpleMint and BulkClaimTool pages along with routing, utilities, and Vercel configuration
eb3c2c8d
main
6/562 ++ 30 --
Merge 7a17f1dd96c4aa02c3c27d204411067717035c41 into a8cffe939423a17871f2df8542c5253d3c148302
51fb3940
pull/47/merge
4/240 ++ 56 --
Merge origin/master into fix/vault-namespace-header
Resolves the conflict in vault.service.spec.ts by taking master's spec and re-applying the namespace test block on top of it. Master added three Vault call sites since the branch point (canCreateUserKey, the shared pqRequest path, kvCreate); they now go through namespaceHeaders() like the rest, and the header table covers all fourteen. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
7a17f1dd
fix/vault-namespace-header
71/5,785 ++ 261 --
fix: send X-Vault-Namespace header on all vault calls
e61c3f3b
fix/vault-namespace-header
4/208 ++ 48 --
Merge 4423646fd1f3b75cc3afcf476364627efcbfd5b8 into 3874f81385d094c5974c5c2afff2af5a2c82b503
615fff4b
pull/6735/merge
17/700 ++ 505 --
Merge ebd1a6151e6ca26613475097f622cce86836f332 into 3874f81385d094c5974c5c2afff2af5a2c82b503
04f651e7
pull/6743/merge
30/4,815 ++ 236 --
Merge 0c06a25c03370ad036d0dd858149a1b46ef876dc into 3874f81385d094c5974c5c2afff2af5a2c82b503
36b5be48
pull/6744/merge
3/277 ++ 3 --
Merge 01ad2e0a03d0f6935a732397654025462e08b597 into 3874f81385d094c5974c5c2afff2af5a2c82b503
e78a5518
pull/6730/merge
1/3 ++ 3 --
Merge 562960a2a1512d3d188f10671303f27c88e5ee6e into 69e6af844b1ecb5787a45f132cce29daaac1cccf
fd5352f7
pull/465/merge
21/1,492 ++ 34 --
Merge f8641deaa14e4ed1cc376726e10355aa7a2fa4cd into 9bc334a8819e21a61e5717e04c07dec184a7c579
6ffae4c1
pull/92/merge
2/56 ++ 42 --
chore(deps): update dependency eslint to v10
f8641dea
renovate/major-eslint-monorepo
2/56 ++ 42 --
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
562960a2
feat/pq-empty-signatures
21/1,492 ++ 34 --
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 --