kivra/jsonformat
67.7
Adequate · 15 November 2026
354
lines of production code
Erlang
primary language
4
measurements over time
What this system is
This system is an Erlang/OTP application focused on providing structured JSON logging capabilities. It includes a custom log formatter that converts standard OTP log messages into single-line JSON output with configurable field mapping and timestamp precision. The project establishes a foundational development environment with dependency management and documentation, but its primary functional contribution is the implementation of the JSON logging infrastructure.
Features
Initial project setup and documentation
This change establishes the project's foundational structure by adding essential configuration files (rebar.config, Makefile, .gitignore), a Renovate configuration for dependency management, and comprehensive documentation (README, CONTRIBUTING, SECURITY). It also sets the minimum required OTP version to 27 and configures the Erlang formatter via the erlfmt plugin.
(repo-wide) · high confidence
Initial release of JSON log formatter
This change introduces the jsonformat application, a custom formatter for the Erlang OTP logger that outputs single-line JSON logs. It provides configurable options for line endings (Unix, Windows, Mac), key mapping to rename log fields, and custom format functions (callbacks) to transform specific data. The formatter handles various log message types, including error reports and standard strings, and supports converting timestamps to ISO 8601 formats with microsecond or nanosecond precision.
src · high confidence
Behavioural changes
Add structured JSON logging configuration
The application now uses a new \sys.config\ file to configure the Erlang/OTP logger. This change switches the default log handler to output structured JSON format (via \jsonformat\) instead of the default plain text, and sets the global log level to \info\.
config · 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 67 → 68 (+0.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.
Lenses
- Code Health 100 → 100 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 61 → 61 (+0.0)
- Readiness 70 → 74 (+4.3)
- Security 77 → 77 (+0.0)
Findings
- No change — the same findings as the prior survey.
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
kivra/jsonformat 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 faec7f6cde7e01e133430699289c405367601484 — 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.