Rust-native Solidity toolchain (forge/cast/anvil/chisel) whose test runner ships all six depth capabilities natively, cut a nightly the same day this was checked off a 953-commit quarter, and publishes Sigstore-signed, SLSA-attested binaries a team can pin and verify — but publishes no framework exit path. Strongest on maintenance that is actually happening (10/10): Re-measured 2026-08-12 07:43Z from artifacts, not copied from the draft — and the draft was already stale. Newest artifact: release tag `nightly-56b854e401f5748989d346f0aea871bac5d3e266`, published 2026-08-12T06:21:36Z (releases.atom), i.e. SAME DAY, not the draft's 2026-08-11 nightly, which is now the second entry.… Weakest on lock-in and documented exit path (8/10): DOWNGRADED from 9.
Dev Frameworks
Dev Frameworks evaluated across maintenance that is actually happening, testing depth the toolchain itself ships, lock-in and documented exit path, and distribution, pinning and disclosure.
Ranked on 4 published criteria weighted 30/30/25/15, which set goal alignment — 30 of the 86 points. The rest: regional access 20, evidence depth 18, ease of use 10, institutional trust 8. Profile match is shown in breakdowns but carries no weight.
What matters most before choosing in this category
Start with whether the thing you are comparing is a toolchain at all, because two of the seven are not. One describes itself as "a combination or stack of other great tools" and hands every testing capability to whichever of Hardhat or Foundry you picked at install; another is an IDE whose own test engine covers two of the six capabilities scored here. Choosing either means you have not yet chosen a toolchain, you have chosen a wrapper around one. Then read maintenance as dated releases rather than popularity, because developer tooling is where a dead project hides best: the stars, the tutorials and the search rank all outlive the final commit by years. Then price the exit, which almost nobody does at adoption time, because the exit bill is denominated in TESTS — the part of a codebase a framework owns most completely. A toolchain whose test language no other toolchain runs is far more expensive to leave than its ergonomics suggest on day one.
Start with whether the thing you are comparing is a toolchain at all, because two of the seven are not. One describes itself as "a combination or stack of other great tools" and hands every testing capability to whichever of Hardhat or Foundry you picked at install; another is an IDE whose own test engine covers two of the six capabilities scored here. Choosing either means you have not yet chosen a toolchain, you have chosen a wrapper around one. Then read maintenance as dated releases rather than popularity, because developer tooling is where a dead project hides best: the stars, the tutorials and the search rank all outlive the final commit by years. Then price the exit, which almost nobody does at adoption time, because the exit bill is denominated in TESTS — the part of a codebase a framework owns most completely. A toolchain whose test language no other toolchain runs is far more expensive to leave than its ergonomics suggest on day one.
Expert review and scoring weights
How this category is reviewed
Reviewed on maintenance that is actually happening, testing depth the toolchain itself ships, lock-in and documented exit path, and distribution, pinning and disclosure.