Ecosystem metrics
- New Repos
- 15
- New
- Commits
- 498
- down 20.7%
- Releases
- 2
- up 0.0%
- Contributors
- 39
- down 4.9%
- Merges
- 14
- up 16.7%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
9001 commits in all time
Aug 07, 2026 08:42 – Nov 05, 2026 08:42 UTC
feat: support Falcon25 seed vault accounts for Liquid Stream (#463)
Co-authored-by: Michael T Chuang <github@michaeltchuang.com>
79ca54b8
main
39/872 ++ 116 --
refactor: change solana seedvault passkey keystore location
ad2ba2bb
pull/463/head
11/191 ++ 54 --
Merge 7b648f9d69c64e2b4a1469598bc58951d3d47237 into bc93c90bacf88000f70d3ba730c3697f81a0c1dd
6f61ab0f
pull/463/merge
37/735 ++ 116 --
refactor: fix seed vault passkey issue
7b648f9d
pull/463/head
17/368 ++ 30 --
Merge 702252ad5697b6108324fd72111494da6d0b1262 into f33aa8c2d6272841aad1705951ca84aaf1d16f56
88e3e04d
pull/66/merge
10/1,194 ++ 980 --
chore(deps): Update all non-major dependencies
702252ad
renovate/all-non-major-dependencies
10/1,194 ++ 980 --
Merge 2b1726e288a61e076209a74748d790bc35ef4cca into f33aa8c2d6272841aad1705951ca84aaf1d16f56
1e8b0cfb
pull/76/merge
3/134 ++ 253 --
chore(deps): Update dependency vitest to v4 [SECURITY]
2b1726e2
renovate/npm-vitest-vulnerability
3/134 ++ 253 --
chore(ci): publish Vue with npm trusted publishing only (#84)
The Vue release still passed the NPM_TOKEN secret, set 2026-06-08 for the package's first publish. That token has expired, so `npm publish` for 1.1.0 failed with E404 on the PUT. Drop the token so the workflow authenticates through trusted publishing (OIDC), as release.yml does.
f33aa8c2
main
1/3 ++ 8 --
Merge 84dd10df6ffe554016b283b49996b89d992072dd into 3a57a165c8c9def630b88dc652d8ec074e63ae4a
c4931fb5
pull/84/merge
1/3 ++ 8 --
chore(ci): publish Vue with npm trusted publishing only
The Vue release still passed the NPM_TOKEN secret, set 2026-06-08 for the package's first publish. That token has expired, so `npm publish` for 1.1.0 failed with E404 on the PUT. Drop the token so the workflow authenticates through trusted publishing (OIDC), as release.yml does.
84dd10df
chore/vue-release-trusted-publishing
1/3 ++ 8 --
Merge c379c3f0470614c2762258e0f787d8065042d345 into 3a57a165c8c9def630b88dc652d8ec074e63ae4a
40c6f509
pull/66/merge
10/1,194 ++ 980 --
chore(deps): Update all non-major dependencies
c379c3f0
renovate/all-non-major-dependencies
10/1,194 ++ 980 --
Merge 85aa7a97e6cf73d215fa846ac865981ad6c98310 into 3a57a165c8c9def630b88dc652d8ec074e63ae4a
bcce7009
pull/76/merge
3/134 ++ 253 --
chore(deps): Update dependency vitest to v4 [SECURITY]
85aa7a97
renovate/npm-vitest-vulnerability
3/134 ++ 253 --
Merge adf46bd9b7e3d4a1f33f3605c9bd3bb71cd961d5 into 3a57a165c8c9def630b88dc652d8ec074e63ae4a
02d032b7
pull/66/merge
10/1,194 ++ 980 --
chore(deps): Update all non-major dependencies
adf46bd9
renovate/all-non-major-dependencies
10/1,194 ++ 980 --
Merge 8cc1e41002788b448a10bb3afb9e8cc81cc06c80 into 3a57a165c8c9def630b88dc652d8ec074e63ae4a
33a85be8
pull/76/merge
3/134 ++ 253 --
chore(deps): Update dependency vitest to v4 [SECURITY]
8cc1e410
renovate/npm-vitest-vulnerability
3/134 ++ 253 --
Notes added by 'git notes add'
5d10b7ac
notes/semantic-release-v1.3.0
1/1 ++ 0 --
chore(release): 1.3.0 [skip ci]
# [1.3.0](https://github.com/TxnLab/use-wallet-ui/compare/v1.2.1...v1.3.0) (2026-11-05) ### Features * support @txnlab/use-wallet v5 ([15c01e9](https://github.com/TxnLab/use-wallet-ui/commit/15c01e95e72db5950fa7c07e7f9b3cbba84f7cfe))
3a57a165
main
2/8 ++ 1 --
chore(ci): use Node 24 LTS and its bundled npm in releases
`npm install -g npm@latest` started installing npm 12, which requires Node ^22.22.2. CI ran Node 22.22.0 from .nvmrc, so both release workflows have failed with EBADENGINE since npm 12.0 (2026-07-08). Move to Node 24.22.2, whose bundled npm 11.19.1 supports trusted publishing, and drop the global npm update step from both release workflows. npm now changes only with .nvmrc, so a new npm major can't silently break releases again. Move the Renovate Node and @types/node pins to 24.x.
1f678ba1
main
4/5 ++ 11 --
chore(ci): use Node 24 LTS and its bundled npm in releases
`npm install -g npm@latest` started installing npm 12, which requires Node ^22.22.2. CI ran Node 22.22.0 from .nvmrc, so both release workflows have failed with EBADENGINE since npm 12.0 (2026-07-08). Move to Node 24.22.2, whose bundled npm 11.19.1 supports trusted publishing, and drop the global npm update step from both release workflows. npm now changes only with .nvmrc, so a new npm major can't silently break releases again. Move the Renovate Node and @types/node pins to 24.x.
187c64bc
chore/pin-npm-11-release
4/5 ++ 11 --
chore(deps): Update Node.js to v22.23.4
8c76068b
renovate/node-22.x
1/1 ++ 1 --