Wassette: A security-oriented runtime that runs WebAssembly Components via MCP
This week brought a new release with v0.8.0, accompanied by a round of dependency upgrades across Rust and Node.js packages. A CI failure was also resolved to keep the build stable.
Get this in your inbox every Monday →A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in wassette's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
chore(deps): Bump proxy-addr from 2.0.7 to 2.0.8 in /tests/mcp-inspector (#869)
chore(deps): Bump fast-uri from 3.1.7 to 3.1.8 in /tests/mcp-inspector (#861)
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.