Ecosystem metrics

New Repos
11
New
Commits
657
up 37.4%
Releases
2
down 66.7%
Contributors
57
up 21.3%
Merges
11
down 31.3%

Repository Explorer

7300 commits in all time Jun 23, 2026 23:20 – Sep 21, 2026 23:20 UTC
ipaleka widgets
Updated documentation configuration
Git Commit f795f292 Branch main Document 7/241 ++ 7 --
ipaleka widgets
Updated documentation configuration
Git Commit c1c7ed8b Branch main Document 5/53 ++ 7 --
ipaleka widgets
Updated documentation configuration
Git Commit bf1d3ce1 Branch main Document 4/42 ++ 5 --
Merge 8cd85a162f6ce98e7694ad71d7863d5ef951c48e into 9bc334a8819e21a61e5717e04c07dec184a7c579
Git Commit ccd6154e Branch pull/73/merge Document 2/206 ++ 328 --
chore(deps): update semantic-release monorepo
Git Commit 8cd85a16 Branch renovate/major-semantic-release-monorepo Document 2/206 ++ 328 --
ipaleka widgets
Implemented total percentage alerts
Git Commit 0f6d90ce Branch main Document 10/520 ++ 45 --
ipaleka widgets
Implemented ASA prices in the alerts
Git Commit 5d925e98 Branch main Document 10/722 ++ 43 --
ToysToTinkerWith DarkCoin
Use permanent published release URLs for asset restoration
Git Commit e0d2cf45 Branch backup/website-and-playground-2026-09-21 Document 3/41 ++ 37 --
ToysToTinkerWith DarkCoin
Complete verified 3D asset recovery archive and restoration tools
Git Commit 6b602354 Branch backup/website-and-playground-2026-09-21 Document 10/149,350 ++ 126 --
ipaleka widgets
Added alerts' evaluate module to decide which rules just fired, from what the engine published
Git Commit dfc911a8 Branch main Document 8/831 ++ 27 --
ToysToTinkerWith DarkCoin
Preserve source filename case for recovery on Linux
Git Commit 42d896f8 Branch backup/website-and-playground-2026-09-21 Document 3/0 ++ 0 --
ToysToTinkerWith DarkCoin
Preserve exact recovery snapshot bytes and record file checksums
Git Commit 5ca216cd Branch backup/website-and-playground-2026-09-21 Document 162/90,384 ++ 90,375 --
ToysToTinkerWith DarkCoin
Back up current website and playground runtime assets with recovery instructions
Git Commit 89d66109 Branch backup/website-and-playground-2026-09-21 Document 300/75,726 ++ 29,003 --
Merge 56825aa12062cb7ced7956bfd1a60b9d6ef75e85 into 3840d6f5e8c73e27141c5752d311c54c2efcf892
Git Commit 312da7a0 Branch pull/36/merge Document 7/324 ++ 13 --
Merge 21f4a1e2040623f131e5df3f3c73ddfce04faa98 into 3840d6f5e8c73e27141c5752d311c54c2efcf892
Git Commit 4b9bd45f Branch pull/35/merge Document 2/31 ++ 3 --
Merge 93793e0099ee0902f652528cbad91f0ff5933084 into 3840d6f5e8c73e27141c5752d311c54c2efcf892
Git Commit 84206180 Branch pull/34/merge Document 3/152 ++ 10 --
fix: wipe byte material when sealing rejects
put() zeroed the caller's buffer only on the success path, so a host
Subtle that rejects the encrypt left the plaintext behind in the array it
was handed. Wipe it in a finally, matching the guarantee use() already
makes for decrypted material.
Git Commit 21f4a1e2 Branch pull/35/head Document 2/31 ++ 3 --
feat: allow an externally supplied vault master key
The vault mints its AES-GCM master key itself and stores it beside the
material it seals, so a copy of the profile directory opens that material
with no secret. Add a `masterKey` provider to the IndexedDB driver, to
createWebKeyStore and to the WithKeyStore extension, for callers that want
the key bound to something the browser cannot produce alone — derived from
a user password, or held by another context.

The provider is resolved per sealing or opening operation rather than
captured in `ready`, so it may reject while a vault is locked and resolve
once it is open. With one set the vault mints no key of its own, `clear()`
stops preserving a record that seals nothing this driver writes, and the
driver reports nativeCryptoKey: false so that keys which would otherwise
persist as non-extractable CryptoKeys are sealed with the supplied key too.

Adopting it is a migration, not a flag, and the docs say so: material the
default vault already sealed stops opening, since `use()` asks the provider
for a key that did not seal it. Sealing standard keys also means their bytes
are decrypted into JS memory for each use. Both limits are pinned by tests.
Git Commit 56825aa1 Branch pull/36/head Document 6/296 ++ 13 --
Merge c49bc0d9370106e981546d139509d8b390d63af4 into b0a3e71a91adfd1dfb97b5060d054618c2a147aa
Git Commit 6751a9a9 Branch pull/66/merge Document 10/1,214 ++ 1,283 --
chore(deps): Update all non-major dependencies
Git Commit c49bc0d9 Branch renovate/all-non-major-dependencies Document 10/1,214 ++ 1,283 --
chore: v2026.37.0 (release)
## [2026.37.0](https://github.com/michaeltchuang/a-day-in-my-bobalife/compare/v2026.36.0...v2026.37.0) (2026-09-21)

### Updates & Maintenance

* log greeting (2026-09-15) ([5587dee](https://github.com/michaeltchuang/a-day-in-my-bobalife/commit/5587deeeebce00e038e465be6b76c91f818d551e))
* log greeting (2026-09-16) ([bec2a77](https://github.com/michaeltchuang/a-day-in-my-bobalife/commit/bec2a7756bd074e105daa2501c0bef1e277780e6))
* log greeting (2026-09-17) ([bd03815](https://github.com/michaeltchuang/a-day-in-my-bobalife/commit/bd038156bc8c7948258e1df9de00449b226cc34a))
* log greeting (2026-09-18) ([775c817](https://github.com/michaeltchuang/a-day-in-my-bobalife/commit/775c8171c55b1223e06181cea44413781f95252d))
* log greeting (2026-09-19) ([b31bd4a](https://github.com/michaeltchuang/a-day-in-my-bobalife/commit/b31bd4a6b28ed7d1aa7140ec384d10b43fd05134))
* log greeting (2026-09-20) ([eb3c3e0](https://github.com/michaeltchuang/a-day-in-my-bobalife/commit/eb3c3e04a5fa2dad1f6bd1f37087e9dc756fedb1))
* log greeting (2026-09-21) ([f1db816](https://github.com/michaeltchuang/a-day-in-my-bobalife/commit/f1db81688487e1e6e8f850f7ee2ed70e701f89f7))
Git Commit dccf7c34 Branch main Document 1/13 ++ 0 --
ipaleka widgets
Added population module which tells the engine which pages have rules on them
Git Commit 3a63a36b Branch main Document 4/264 ++ 1 --
fix: serialise vault master-key creation across contexts
Every same-origin context that builds an IndexedDB driver reaches
getMasterKey concurrently on first use. All of them missed the read, all
generated a key, the last put won, and each context kept using the key it
had generated itself, so material sealed by one could not be opened by
another — surfacing as a bare AES-GCM OperationError.

Mint the key under a Web Lock and re-read once the lock is held, so the
first caller creates and the rest reuse what it wrote.
Git Commit 93793e00 Branch pull/34/head Document 3/152 ++ 10 --
Argimirodelpozo puya
Merge fe10b9fe883bd2e98bb6dc7896c05142b0e691cc into 27751c364229ae3cd0334fe4071e61690b6879e4
Git Commit 56f96169 Branch pull/751/merge Document 300/209,555 ++ 10,346 --