What's new in Cejel

Certificate text stays inside its tooltip. Long unbroken metric descriptions now wrap inside the HTML certificate tooltip instead of overflowing its fixed-width box.

A named rubric must actually run. The sealed scoring path now rejects an explicitly supplied rubric version that is not wired into public dispatch, rather than issuing a certificate that names a rubric which did not execute. The release also adds clean-runner checks for the Smithery and OpenClaw MCP routes.

Inspect the v0.4.4 release → · Read the release notes →

Closes the stale-version trap. Every documented CLI invocation across the README, leaderboard site copy, and the calibration issue template now pins @latest or an explicit version, so npx @cejel/cejel can no longer silently resolve a stale cached package. A guard test fails the build if an unversioned invocation is reintroduced.

Readability fixes. Certificate tooltips now sit clearly above the page instead of blending into the content behind them. The Markdown certificate now carries the CLI version, matching the HTML and JSON certificates. Several metric labels and finding lists were corrected for consistency and accuracy across all three certificate formats. The release also states the recognized-CI boundary: which systems Cejel treats as real CI signal, and how that set can only change through a version-gated rubric change.

Inspect the v0.4.3 release → · Read the release notes →

A read-only currency verifier independently checks every supported release surface — npm, OCI, the MCP Registry, and GitHub — and fails closed on stale, unreachable, or inconsistent state, rather than trusting any one surface’s self-report.

Certificate clarity. Human-readable terminal, HTML, and Markdown certificates now include relying-party summaries, consistent measurements, and a plain-English glossary informed by external reviewer feedback. OCI distribution readback now authenticates before verifying the published image’s attestation and tagged source, and public-distribution validation rejects location fields and private-path-shaped text in public transparency artifacts.

Inspect the v0.4.2 release → · Read the release notes →

Byte-identical reports regardless of checkout location. report.json no longer embeds the absolute checkout path, so identical repository content and revision scanned in different directories produce byte-identical report artifacts. Reports from v0.4.0 and earlier keep their recorded path and remain verifiable.

Nothing else changed. This is a single-fix patch release: no scoring, rubric, certificate, or CLI behavior change. Prospective rubrics and in-development detector proposals remain unreleased.

Inspect the v0.4.1 release → · Read the release notes →

Stronger publication verification and two explicitly bounded prospective tools. The distribution workflow now reads the published MCP Registry record back, requires its immutable OCI digest, and verifies that digest’s signed provenance against the exact release tag and source commit. The release also carries prospective rubric v19 and a resource-bounded v2 discovery collector for explicit evaluation harnesses.

No silent scoring promotion. The v19 paired rescore completed all 24 rows with no score, status, coverage, placement, or non-B4 changes. It remains prospective; the public CLI default is still the separately holdout-calibrated v17 rubric. The v2 collector does not change the SHA-pinned v1.9 contract or ship the reserved Free LLM command family.

Inspect the v0.4.0 release → · Read the release evidence boundary →

The published npm, Docker / OCI, standalone-binary, and MCP Registry release. Its published GitHub Release includes five native binaries, SPDX SBOMs, SHA256SUMS, and signed provenance. The source record names the v0.3.2 commit.

Run the source-verification commands →

The v0.3.1 npm and Docker / OCI release. Its source record names the v0.3.1 commit, so a reader can inspect the tagged source rather than rely on a release claim.

Run the source-verification commands →

Windows binaries — Cejel now ships a standalone single-file executable on all five platforms: macOS (Apple silicon + Intel), Linux (arm64 + x64), and Windows (x64). No Node, no npm, nothing installed. Every binary has an SPDX SBOM and SHA-256 checksum; the release also includes GitHub-signed build provenance, while own-platform verification receipts remain attached to the guarded build — because a trust tool you can’t verify is just another black box.

It runs inside your AI coding agent. Cejel is now documented as an MCP server you can add to OpenClaw (or any MCP client) through the shipped cejel-mcp bin, so an agent can check a repository’s evidence before you rely on it. It scans code you point it at — it does not watch or govern the agent’s actions.

Sharper certificates. Certificates now show both the producing CLI version and the exact rubric version, so reports from different installs explain their scoring identity. A dimension band that differs from the weighted score now carries an inline reconciliation instead of a bare number next to “verified.” A scan of a source tarball now warns when Git history was unavailable and a recent-PR metric may undercount. And the install docs force @latest to sidestep a stale npx cache. Thanks to the early testers who reported these.

Also folded in from main: hardened Git transport at the clone/checkout sinks, the free-core v50 multiple-comparisons disclosure, and a cross-repo preflight gate. Full commit-linked detail: CHANGELOG.md.

0.2.1 was an npm-only certificate-presentation patch. 0.2.0 established the scoped public distribution: standalone binaries for macOS and Linux, the OCI image, and the Official MCP Registry listing. The complete history lives in the repository changelog.