Skip to content
CAI
Software that uses CAICheck a score

eproxus/kraft

48.2

Weak · 15 November 2026

2.1k

lines of production code

Erlang

with JavaScript

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add Kraft REST API example with client-side templating

Introduces a new REST API example application that serves a static HTML interface powered by htmx, Mustache, and a client-side templates extension. The example exposes a JSON endpoint at /api/v1/example/endpoint and renders the response using a Mustache template on the client side, demonstrating how to integrate server-side JSON responses with client-side rendering in a Kraft application.

examples/rest · high confidence

Add Kraft blog example application

A new example application demonstrating a blog built with Kraft is now available in the examples/blog directory. It includes the necessary source files (blog.erl, controllers, supervisor) and configuration to run a sample site on port 8091, serving static assets and rendering templates for posts and pages.

examples/blog · high confidence

Add Kraft chat example with WebSocket support

Introduces a new chat example application in \examples/chat\ that demonstrates real-time communication using Kraft's WebSocket capabilities. The example includes an Elixir/Erlang backend (\chat.erl\, \chat\_room.erl\) that manages a chat room via the \pg\ module and serves static assets, including a bundled copy of htmx (v1.4.1) for client-side interactivity. It also provides the necessary build configuration (\rebar.config\, \chat.app.src\) and Mustache templates to render the chat interface.

examples/chat · high confidence

Add Kraft examples index application

Introduces a new example application that serves as a central index for the Kraft framework's demo apps. It provides a static landing page linking to individual examples (Blog, Web Socket, Chat, REST API, TODO) and includes dedicated routes to demonstrate error handling, specifically triggering 404, 500, and missing template errors for testing purposes.

examples/index · high confidence

Add WebSocket example application with raw, JSON, and JSON-RPC handlers

The examples/ws directory now includes a complete demonstration application for Kraft's WebSocket capabilities. It provides three distinct handler types: a raw text handler at /raw/ws, a JSON handler at /json/ws, and a JSON-RPC handler at /jsonrpc/ws that supports automatic ping/pong keep-alives. The example includes static HTML pages for each mode to facilitate testing and demonstrates features such as echo responses, method calls, notifications, and connection closure.

examples/ws · high confidence

Add blog example with dark mode support

The blog example now includes a complete set of Mustache templates and Tailwind CSS styles that support dark mode. Users will see the blog interface adapt to their system's color scheme preferences, with specific styling for the header, footer, post listings, and individual post pages.

examples/blog/priv/web · high confidence

Added example configuration with info-level logging

An example configuration file has been added to the project, setting the kernel logger level to 'info'. This provides a reference configuration for users to understand the default logging verbosity.

config · high confidence

Introduction of configurable template and render caching with ETS backend

The framework now supports caching for templates and rendered content to improve performance. A new \kraft\_cache\ behavior defines the interface, implemented by \kraft\_cache\_ets\ which uses Erlang ETS tables. The cache configuration is exposed in \kraft.app.src\ under the \kraft\ application environment, allowing users to set memory limits (e.g., \{mib, 64}\), age limits (e.g., \{minute, 5}\), and cleaning intervals. The \kraft\_instance\ module initializes these handlers per application, and the \kraft\_dev\ module integrates with this caching during development template reloading.

src · high confidence

Behavioural changes

Blog example uses Tailwind CSS v4 with on-demand build

The blog example now styles its UI using Tailwind CSS v4. The styles are defined in a single CSS file that imports the Tailwind framework and specifies the source directory, and the build process is configured to generate styles on demand via a Makefile symlink.

examples/blog/priv/styles · high confidence

Enforce code analysis and formatting on commit

A new pre-commit hook has been added to the repository that automatically runs \rebar3 analyze\ and \rebar3 fmt --check\ before allowing a commit. This ensures that all code changes meet the project's static analysis standards and formatting guidelines, preventing unanalyzed or improperly formatted code from being committed.

.githooks · high confidence

Introduce automated changelog generation and update core dependencies

The project now uses git-cliff to automatically generate the CHANGELOG.md from conventional commits, supported by a new cliff.toml configuration. This release also updates Cowboy from 2.8.0 to 2.19.0, cowlib to 2.20.0, and ranch to 2.3.0, while adding mapz as a new dependency. Additionally, the framework now requires Erlang/OTP 27.0 or later due to the replacement of the jsx library with the OTP JSON module.

(repo-wide) · high confidence

Migrate to Tailwind CSS v4 build system

The styles build process has been updated to use Tailwind CSS v4, replacing the previous v3 configuration. The explicit \tailwind.config.js\ file has been removed in favor of the new \@import "tailwindcss"\ directive in \kraft.css\, and a new Makefile has been introduced to manage the CSS compilation and watch tasks.

priv/styles · high confidence

Redesigned error pages with dark mode support and improved stack trace readability

The web application's error handling UI has been completely overhauled to provide a modern, responsive experience with full dark mode support. The previous static 404 and 500 templates have been replaced with a unified layout system that dynamically renders error details, including a new, highly readable stack trace view in the footer that formats module, function, and file paths with clickable links. The design now adapts to the user's system preferences, switching between light and dark color schemes for backgrounds, text, and borders. Additionally, the CSS asset path has been updated to reflect the new Tailwind v4.1.4 build, ensuring consistent styling across all error states.

priv/web · high confidence

Todo example now uses Tailwind CSS and htmx for the UI

The todo example has been updated to use a modern frontend stack. It now includes Tailwind CSS (v3.4.3) with the DaisyUI and Typography plugins for styling, replacing previous approaches. Additionally, htmx (v1.9.12) is bundled as a static asset to enable asynchronous, partial page updates without writing custom JavaScript. A Makefile and configuration files have been added to build the CSS from source templates.

examples/todo · high confidence

Dependencies

Upgrade Tailwind CSS and update styling dependencies

The project's styling tooling has been upgraded from Tailwind CSS 2.1.2 to 3.3.1. This change replaces the previous dependency set (which included autoprefixer, postcss, and postcss-import) with a modern configuration that includes the @tailwindcss/forms and @tailwindcss/typography plugins, as well as the daisyui component library. Users will benefit from the latest Tailwind features and pre-built UI components while the underlying build process is streamlined.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 49 → 48 (-0.6)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

Lenses

  • Code Health 99 → 98 (-0.6)
  • Architecture 99 → 99 (+0.0)
  • Maturity 53 → 53 (+0.0)
  • Readiness 39 → 39 (-0.1)
  • Security 94 → 90 (-4.6)
  • Accessibility 38 → 38 (-0.5)

Resolved (2)

  • Medium CVE: EEF-[CVE redacted] (rebar.lock)
  • No tests found

New (7)

  • Edited copy of a member (4 corresponding lines) (examples/blog/src/blog_page.erl)
  • Edited copy of a member (6 corresponding lines) (examples/index/src/index.erl)
  • Edited copy of a member (8 corresponding lines) (examples/blog/src/blog.erl)
  • Medium CVE: EEF-[CVE redacted] (rebar.lock)
  • Medium CVE: EEF-[CVE redacted] (rebar.lock)
  • Outdated: cowboy
  • Outdated: cowlib

Changes since last survey

  • 6 commits — 6 feature/other, 0 fixes

By area

  • .github/workflows — 4 commits
  • (root) — 2 commits

Notable commits

  • change: chore(deps): update dependency rebar to v3.28.0 (#60)
  • change: chore(deps): update jdx/mise-action action to v5.2.1 (#58)
  • change: chore(deps): update jdx/mise-action action to v5.2.2 (#59)
  • change: chore(deps): update jdx/mise-action action to v5.2.3 (#61)
  • change: chore(deps): update jdx/mise-action action to v5.2.4 (#62)
  • change: chore(deps): update jdx/mise-action action to v5.2.5 (#63)

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

eproxus/kraft was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 15 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit e3c69b90f07aac2de62e42195f6c431cb2e1f70c — the exact code this score is about.
  • Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.65+preprod-3c33c1882dc1.