Ecosystem metrics

New Repos
14
New
Commits
561
down 30.2%
Releases
7
up 75.0%
Contributors
45
up 12.5%
Merges
7
down 81.1%

Repository Explorer

6976 commits in all time Jun 10, 2026 10:10 – Sep 08, 2026 10:10 UTC
bwmx intermezzo
Merge 25b4299c4a61d7ea5aae54f99d727432ab4e50a4 into ec6c593a804c81f661cf4c003f17ff964d9cae95
Git Commit 4f75898e Branch pull/40/merge Document 27/2,483 ++ 53 --
bwmx intermezzo
docs: record the algosdk pqsig blocker in the PQ accounts plan
Bring the plan in line with what increments 1 and 3 actually shipped, and settle
the increment 4 design against the published SDKs.

algokit-utils cannot emit a pqsig envelope in any released version - checked
through 10.0.0-beta.4, the newest on npm - so increment 4 cannot be written
against the packages currently installed. algosdk 3.7.0 has the full feature:
SignedTransaction.pqsig, EncodedPQSig, addressFromPQKey/addressFromPQSig, an
async remote-signer adapter shaped like a Vault call, and an empty-signature
signer that makes algod report the real post-quantum fee under simulate.

Adding algosdk 3.7.0 is therefore a hard prerequisite for increment 4, scoped to
the PQ envelope and address helpers only; transaction building, grouping and
encoding stay on algokit-utils. That supersedes the earlier plan to hand-assemble
the envelope and promote algorand-msgpack to a direct dependency - hand-rolling
canonical msgpack on a money path is the wrong trade when the SDK's own schema
encoder is available.

The two SDKs interoperate at the byte level, verified against the real packages:
algosdk decodes algokit's encoded transaction (TX prefix stripped) and re-encodes
it byte-identically, its bytesToSign output matches algokit's encodeTransaction
exactly, an ed25519 signed transaction encodes identically under both, and the PQ
address helpers agree with the Vault plugin's derivation.

The rest tracks reality: increment 4 is no longer blocked on an unavailable algod
version now that v5 is released, the increment 1 notes describe the plugin
version pinning and mount verification that were built, account_type is required
rather than optional, the signing call sites still discard the resolved
UserAccount, and the review findings increment 4 has to clear are listed
explicitly alongside the non-atomic cross-mount check left for cleanup.
Git Commit 25b4299c Branch feat/pq-accounts Document 1/143 ++ 44 --
bwmx intermezzo
Merge 01b3e53e99c56603c8aee6851007112c515a8a02 into ec6c593a804c81f661cf4c003f17ff964d9cae95
Git Commit c8532330 Branch pull/40/merge Document 27/2,395 ++ 53 --
bwmx intermezzo
docs: update PQ accounts implementation plan
Git Commit 01b3e53e Branch feat/pq-accounts Document 1/22 ++ 11 --
bwmx intermezzo
chore(localnet): require algod v5
Git Commit e26871d2 Branch feat/pq-accounts Document 1/14 ++ 1 --
bwmx intermezzo
feat(vault): harden PQ plugin lifecycle
Git Commit 8f1265c9 Branch feat/pq-accounts Document 5/46 ++ 10 --
Merge b4b5e801aacd94ae723ac7f35b985f0e6a746aff into 7861a68efdc034d4a01f5ba68f1acff97e28e8e6
Git Commit fd604d8c Branch pull/454/merge Document 15/1,412 ++ 967 --
chore(deps): update non-major dependencies
Git Commit b4b5e801 Branch renovate/non-major-dependencies Document 15/1,412 ++ 967 --
Merge 202ec4eda170b1fbe64a8edeef53264bf5e50674 into dd7be47db270b641b07a8abb0bb3995360a8e34f
Git Commit 34603a25 Branch pull/915/merge Document 1/1 ++ 1 --
build(deps-dev): update eslint requirement from ^10.9.1 to ^10.10.0
Updates the requirements on [eslint](https://github.com/eslint/eslint) to permit the latest version.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](https://github.com/eslint/eslint/compare/v10.9.1...v10.10.0)

---
updated-dependencies:
- dependency-name: eslint
  dependency-version: 10.10.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Git Commit 202ec4ed Branch dependabot/npm_and_yarn/eslint-tw-10.10.0 Document 1/1 ++ 1 --
Merge 2f864bc0759d6078b7a630006d266192679f15f4 into ae593f700fcba41d7f4accba74cf33549a96c3f4
Git Commit 0ed4ee45 Branch pull/355/merge Document 42/11,806 ++ 0 --
fix: top up action from viewer end for liquid stream (#404)
Co-authored-by: Michael T Chuang <github@michaeltchuang.com>
Git Commit 35e28988 Branch main Document 7/48 ++ 35 --
renovate[bot] use-wallet
Merge a2871ec5d01d3001ce0d7a2387618a9830872c3c into 7861a68efdc034d4a01f5ba68f1acff97e28e8e6
Git Commit b1c01f06 Branch pull/449/merge Document 1/1,312 ++ 1,272 --
renovate[bot] use-wallet
chore(deps): lock file maintenance
Git Commit a2871ec5 Branch renovate/lock-file-maintenance Document 1/1,312 ++ 1,272 --
ipaleka frontend
Bugfix for quote-signed group which cannot carry the opt-in
Git Commit b81327f5 Branch main Document 1/1 ++ 1 --
ipaleka widgets
Bugfix for quote-signed group cannot carry the opt-in
Git Commit b82d6e80 Branch main Document 2/106 ++ 0 --
Merge 7dc7604b81a179f62eeb7ae95edb637021159e08 into 361d3066ffaca4241991cc6563403417bf562ecf
Git Commit f0bec789 Branch pull/23/merge Document 1/4,207 ++ 3,552 --
chore(deps): lock file maintenance
Git Commit 7dc7604b Branch renovate/lock-file-maintenance Document 1/4,207 ++ 3,552 --
Merge 24aafb2ab114f67ddb1857d5391de1d89abfe95a into 9bc334a8819e21a61e5717e04c07dec184a7c579
Git Commit 60803737 Branch pull/73/merge Document 2/204 ++ 330 --