bytecodealliance/wasmtime vs wasmerio/wasmer
Both showing Healthy signals — pick on fit, not health
As of September 2026, wasmtime and wasmer both show healthy maintenance signals. wasmtime was committed to 1 day ago with 25+ active contributors, while wasmer was committed to 1 day ago with 9+ active contributors. wasmtime is Apache-2.0-licensed while wasmer is MIT-licensed. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
bytecodealliance/wasmtime
Healthy across all four use cases
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ⚠Scorecard: dangerous CI workflow (0/10)
- ⚠9 moderate-severity advisories on direct dependencies
- ✓Last commit today
- ✓25+ active contributors
- ✓Distributed ownership (top contributor 33% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
wasmerio/wasmer
Healthy across all four use cases
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ⚠Concentrated ownership — top contributor handles 56% of recent commits
- ✓Last commit today
- ✓9 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
Signal-by-signal breakdown
| wasmtime | wasmer | |
|---|---|---|
| Stars | 18,639 | 21,029 |
| Last commit | 1d ago | 1d ago |
| License | Apache-2.0 | MIT |
| Open issues | 847 | 270 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 100% |
| Dependency CVEs | 0 critical · 0 high · 9 moderate · 0 low | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? bytecodealliance/wasmtime · wasmerio/wasmer
Ask AI about bytecodealliance/wasmtime vs wasmerio/wasmer
Open the chat with a comparison question pre-filled.