MAIF/izanami
48.1
Weak · 7 November 2026
58.1k
lines of production code
Scala
with TypeScript
4
measurements over time
What this system is
Features
Add Swagger UI and OpenAPI specification for client API documentation
Developers can now view the Izanami client API documentation via a Swagger UI interface. This change introduces a new static Swagger UI page (version 5.15.0) and an OpenAPI 3.0.3 specification file (swagger.json) that details the client endpoints, including feature activation checks and server-sent event subscriptions. Note that the specification explicitly excludes admin endpoints used by the backoffice.
manual/static/swagger · high confidence
Database schema migrations for audit logging, personal access tokens, and role-based rights
This update applies a series of database schema migrations (V11–V24) that introduce foundational support for new security and auditing capabilities. It creates the \global\_events\ table and sequence to track tenant and project lifecycle changes, including timestamps, origin, and authentication method. It establishes the \personnal\_access\_tokens\ table and associated rights table, progressively adding granular permissions such as read, update, and delete for features, projects, keys, and tenants. Additionally, it introduces \PROJECT\_RIGHT\_LEVEL\ for finer-grained project access control, adds a \roles\ JSONB column to users for OIDC role mapping, and enforces text size constraints on tenant, user, and configuration fields to ensure data integrity.
conf/sql/globals · high confidence
Dataset export and import capabilities added
The system now supports exporting and importing datasets, as evidenced by the modification of the dataset files (with-users.ndjson and without-users.ndjson). This change enables users to move data in and out of the system, facilitating data portability and backup processes.
datasets · medium confidence · unverified
Frontend UI overhaul: dark/light mode, new pages, and dependency migration
The frontend has been significantly updated with a new dark/light theme toggle (persisted via local storage), a migration from react-query to @tanstack/react-query, and the addition of several new pages and features including Swagger integration, Webhooks management, Project and Tenant audit logs, Atomic Design, and a dedicated Tags list page. The UI also introduces a new Loader component, input confirmation modals for destructive actions, and various styling improvements using CSS variables for better theming support.
izanami-frontend/src · high confidence
Frontend migration to TanStack Query and new management pages
The frontend has migrated its data-fetching layer from \react-query\ to \@tanstack/react-query\, updating all page components (including Home, Login, Menu, Keys, GlobalContexts, and others) to use the new query/mutation configuration syntax and the shared Loader component. This change introduces several new management capabilities: a dedicated Tags page for creating, editing, and bulk-deleting tags; Webhooks management for configuring and scoping webhooks; Swagger UI integration for API documentation; and Project/Tenant Audit Log pages for tracking feature and entity changes. Additionally, the Global Contexts page now supports context protection updates, and the login experience includes a light/dark mode toggle.
izanami-frontend/src/pages · high confidence
Introduce granular personal access tokens and import/export capabilities
Users can now authenticate and manage Izanami resources using personal access tokens, which support granular tenant and global rights (such as export, import, and feature updates) and can be configured with expiration dates. Additionally, the system now provides dedicated datastore models and types to support importing and exporting tenant data, including features, projects, contexts, and webhooks, with configurable conflict strategies.
repository · high confidence
Introduction of light mode and CSS variable-based theming
The frontend now supports a light theme, switchable via the \[data-theme="light"\] attribute, which redefines background and text colors for various UI levels. This is achieved by migrating from hardcoded hex values in the React Select styling to CSS custom properties (e.g., --bg-color\_level1, --color\_level1), ensuring consistent appearance across both dark (default) and light modes. Additionally, the styling infrastructure was updated to use the modern SCSS @use syntax instead of @import, and new components such as pagination and search modal were integrated into the main stylesheet.
izanami-frontend/src/styles · high confidence
New frontend components for context selection, audit logs, and feature management
The frontend now includes a suite of new UI components to enhance feature flag management and auditing. Users can select contexts via the new AllContextSelect component, which displays a hierarchical tree of global and project contexts. Audit logs are now viewable through the AuditLogs component, supporting filtering by event type, user, and date range with infinite scrolling. Feature details are rendered more clearly using FeatureDetails, which handles boolean, percentage, and non-boolean feature types. The OverloadTable component allows users to manage feature overloads per context, including enabling/disabling and deleting overloads, with confirmation modals for protected contexts. Additionally, the Editor component provides a Handlebars template editor for webhook transformations, and the FeatureSelector allows selecting features by ID or name. The MultiSelect component supports indeterminate states for bulk operations, and the Loader component provides a simple loading indicator.
izanami-frontend/src/components · high confidence
New search modal with tenant selection, filtering, and history
The frontend now includes a new search modal component (SearchModal) that allows users to search across all tenants or a specific one, apply type-based filters (such as Features, Projects, Keys, etc.), and view previous search history. The implementation includes a debounced search input, tenant selection controls, and result grouping by entity type, with search history persisted in local storage.
izanami-frontend/src/components/SearchComponant · high confidence
New standalone Docker image with embedded PostgreSQL for demo
A new Dockerfile (Dockerfile-pg-embeded) and startup script (script.sh) have been added to the demo-docker-image directory, enabling a self-contained demo environment. This image bundles PostgreSQL 17.2 and the Izanami application, automatically starting the database and waiting for it to be ready before launching the Java application, allowing users to run the demo without external database dependencies.
demo-docker-image · high confidence
New web controllers for export, search, webhooks, and personal access tokens
This change introduces several new web controllers in the application layer: ExportController for tenant data export, SearchController for feature and context search, WebhookController for webhook management, and PersonnalAccessTokenController for handling personal access tokens. It also refactors ApiKeyController to use service-based logic and supports personal access token authentication, and updates AuthAction to support new authentication types and user information structures. Additionally, ConfigurationController is updated to include version info and prevent OAuth modification flags, and EventController is refactored to use a new event service and support legacy event formats.
app/fr/maif/izanami/web · high confidence
Webhook delivery with retry, Handlebars templating, and tenant lifecycle management
The system now includes a new WebhookListener that monitors Izanami events and delivers them to configured webhook endpoints. This change introduces support for Handlebars templates in webhook payloads, allowing users to customize the request body. It also adds configurable exponential backoff for retries and a scheduled job to re-attempt failed webhook calls. The listener automatically manages tenant subscriptions, starting for new tenants and stopping for deleted ones, and includes logic to prevent disabled hooks from being triggered.
app/fr/maif/izanami/jobs · high confidence
Removals
Removed Play Scala form scaffolding template
The \.g8/form\ directory, which provided a Giter8 template for generating a Play Scala form controller, view, and associated tests, has been deleted. This removes the ability to scaffold a basic form handling setup with a controller, a Scala HTML view, and unit tests for a specified model.
.g8, .g8/form · high confidence
Behavioural changes
1 commit (0 fixes) modifying (repo-wide)
A change to existing behaviour in (repo-wide) — 1 commit, 64 files: “chore: backend format & format check in CI”. Also in this area: Added cleanup bridge for wasm4s global pools.
app/io · low confidence · unverified
1 commit (0 fixes) modifying izanami-frontend/.husky
A change to existing behaviour in izanami-frontend/.husky — 1 commit, 1 file: “chore: format pre-commit hook (front)”.
izanami-frontend/.husky · low confidence · unverified
Backward-compatible config migration for Izanami cluster settings
The application now automatically migrates legacy string-based configurations for cluster settings into their proper structured formats at startup. Specifically, if \app.cluster.context-blocklist\, \app.cluster.context-allowlist\, \app.cluster.worker-url-by-contexts\, \app.cluster.worker-url-by-contexts-and-tenants\, \context-allowlist-by-tenant\, or \context-blocklist-by-tenant\ are provided as JSON strings instead of native arrays or maps, the system parses and converts them to the expected internal types. This ensures backward compatibility for existing deployments without requiring immediate configuration changes.
app/fr/maif/izanami · high confidence
Database schema overhaul for contexts, webhooks, and feature values
This update applies a series of database migrations (V1–V15) that fundamentally restructure how contexts, features, and webhooks are stored and managed. Contexts are migrated to a hierarchical ltree-based model with enforced global/project consistency and cascading protection rules, allowing projects to be deleted even when contexts exist. Feature values now support negative numbers and non-boolean types (strings, numbers) with stricter validation, while project and tag identifiers switch from UUIDs to text strings. Additionally, a new webhook system is introduced with dedicated tables for tracking call statuses and audit logs, and comprehensive text size constraints are added across all major entities to prevent data overflow.
conf/sql/tenants · high confidence
Datastore layer refactored to direct PostgreSQL access with new feature tracking and search capabilities
The data access layer in the \datastores\ package has been significantly restructured to remove the abstraction over the \Env\ object, replacing it with direct dependencies on \Postgresql\, \EventService\, and other specific components. This change introduces new datastores for tracking feature usage (\FeatureCallsDatastore\), performing fuzzy search across entities like projects, features, and tags (\SearchDatastore\), and managing webhook call statuses (\WebhooksDatastore\). Existing datastores such as \ApiKeyDatastore\, \ConfigurationDatastore\, \FeatureContextDatastore\, \FeaturesDatastore\, and \ProjectsDatastore\ have been updated to use this new direct access pattern, enabling better event emission, tenant-scoped queries, and support for new features like protected contexts and OIDC configuration migration.
app/fr/maif/izanami/datastores · high confidence
Documentation updates for v1.11.5 release and typo fixes
The manual has been updated to reflect the v1.11.5 release, with download links for binaries, Docker images, and the CLI now pointing to the specific version tag instead of the generic 'latest' release. Additionally, various typos in the documentation have been corrected, including fixes for 'Tracability', 'Advanded', 'betwwen', 'conditonal', and 'abilitations', as well as a correction to the OpenAPI Swagger UI path.
manual/v1 · high confidence
Expanded configuration options and new API endpoints for clustering, OIDC, and webhooks
The application configuration now supports cluster mode settings (standalone, leader/worker), context allow/blocklists, and tenant-specific worker URLs, enabling distributed deployments. OIDC authentication is enhanced with configurable scopes, PKCE, and field mappings, while new configuration sections allow tuning webhook retry strategies, stale feature tracking, and PostgreSQL connection lifetimes. Additionally, the routes file introduces endpoints for personal access tokens, webhook management, tenant/project audit logs, search, export/import, and Server-Sent Events (SSE), alongside updates to existing feature and context APIs to support protected context preservation.
conf · high confidence
Frontend infrastructure modernization and test environment stabilization
The frontend development environment has been updated to use the modern ESLint flat config format and Vitest for unit testing, replacing the legacy JSON-based ESLint configuration and removing obsolete database initialization scripts. To improve reliability in CI and local development, Playwright end-to-end tests now run with increased timeouts, single-worker execution, and a more robust web server startup sequence that explicitly waits for backend and frontend health checks. Additionally, the Vite development server is now fixed to port 3000 with a proxy for Swagger API definitions, and static assets like Bootstrap and FontAwesome are served from local node modules instead of external CDNs to ensure consistent builds.
izanami-frontend · high confidence
Frontend utility layer overhaul and expanded API support
The frontend's utility layer has been significantly expanded and refactored to support new product capabilities. New modules were added for context management (\contextUtils\), feature format conversion (\featureUtils\), and user notifications (\toastUtils\), alongside a new default timezone utility. The \patterns\ module now accepts spaces in feature names and personal access token names, and introduces validation for tags and webhooks. API query definitions (\queries\) now include endpoints for personal access tokens, webhooks, and project logs, while \types\ introduces data models for audit logs, import errors, and personal access tokens. Additionally, the \icons\ module was updated to use SVG sprite references for better performance.
izanami-frontend/src/utils · high confidence
Improved error handling with PostgreSQL constraint mapping and separated error logging
Users will now receive more specific and meaningful error messages when database constraints are violated (such as duplicate names, missing required fields, or invalid foreign key references) because a new PostgresErrorMapper translates raw PostgreSQL constraint codes into distinct Izanami error types. Additionally, the HTTP error handler now uses separate loggers for client and server errors, improving the clarity and traceability of error logs in operational environments.
app/fr/maif/izanami/errors · high confidence
Manual site performance and layout improvements
The documentation site now uses a compressed WebP version of the Izanami logo to improve load performance, and the landing page layout has been adjusted to center and wrap content more effectively on smaller screens. Additionally, a new CSS class has been added to ensure checkmark tables are centered.
manual/src · high confidence
Migrate datastore utility to Apache Pekko
The \Datastore\ trait in the \app/fr/maif/izanami/utils\ package has been updated to use Apache Pekko instead of Akka. Specifically, the import for \FastFuture\ now references \org.apache.pekko.http.scaladsl.util.FastFuture\, aligning this utility component with the broader framework migration.
app/fr/maif/izanami/utils · high confidence
Migrate to Scala 3 and modernize development tooling
The project has migrated from Scala 2.13 to Scala 3, requiring updates to the build configuration (\.scalafmt.conf\, \.scalafix.conf\) and the Dockerfile to reflect the new compilation output path. Development workflows have been consolidated using \mise\ and \process-compose\ to manage dependencies and local services, replacing previous manual scripts. Additionally, the local OIDC testing setup has been upgraded from \qlik/simple-oidc-provider\ to \oidc-server-mock\, and the \default-oidc-users.json\ fixture has been removed.
(repo-wide) · high confidence
Migration to Apache Pekko and Play 3 with typed configuration
The application runtime has been upgraded from Akka to Apache Pekko and from Play 2 to Play 3. This change introduces a new typed configuration system (\AppConf\) that replaces direct access to the raw configuration object, providing stricter type safety for settings such as secrets, database connections, and OIDC parameters. The environment initialization now relies on this typed configuration, and the underlying actor system and scheduler are sourced from the Pekko library.
app/fr/maif/izanami/env · high confidence
Migration to Apache Pekko and addition of FutureEither syntax helpers
The application has migrated its underlying actor and HTTP infrastructure from Akka to Apache Pekko, updating all relevant imports (akka.\* to org.apache.pekko.\*). Additionally, new implicit syntax extensions have been added to simplify error handling and type conversion: a \fEither\ method on values to create \FutureEither\ instances, and extension methods on \Future\, \Either\, and \Boolean\ to convert them into \FutureEither\ or Java Boolean types respectively.
app/fr/maif/izanami/utils/syntax · high confidence
Migration to CSS variables and SCSS @use syntax for layout styling
The layout styles in the frontend have been refactored to replace legacy SCSS variables (e.g., $fondBody, $primaryColor) with CSS custom properties (e.g., var(--bg-color\_level1), var(--color\_level2)) and SCSS module imports (@use). This change enables dynamic theming capabilities, such as the newly supported light mode, by allowing colors and backgrounds to be updated via CSS variables rather than hardcoded SCSS values. Additionally, the sidebar positioning was adjusted (top: 50px) and responsive breakpoints were updated to improve layout behavior on smaller screens.
izanami-frontend/src/styles/layout · high confidence
Service layer refactoring and new feature capabilities
The service layer has been restructured into dedicated components (APIKey, Event, Feature, FeatureUsage, Right, Tag, Tenant, and Webhook services) to improve separation of concerns. This update introduces several new capabilities: users can now track stale features based on usage history, OIDC roles are mapped to Izanami rights for external users, and webhook templates support Handlebars helpers. Additionally, protected contexts are better preserved during updates, and the system now supports disabling WASM scripts instance-wide.
app/fr/maif/izanami/services · high confidence
UI component styling modernized and light theme support added
The frontend component styles have been refactored to replace hardcoded color values with CSS variables (e.g., \var(--color-primary)\, \var(--bg-color\_level1)\), enabling consistent theming and easier light mode support. New styles have been added for pagination, search modals, and toast notifications, while existing components like buttons, tables, accordions, and modals have been updated to use the new variable system and improved visual hierarchy.
izanami-frontend/src/styles/components · high confidence
V2 event schema and WasmManager client refactoring
The V1 feature events module now includes a new V2 event schema (V2FeatureEvents) that structures feature lifecycle events (creation, update, deletion, keep-alive) with explicit types, user metadata, and Instant-based timestamps, while retaining the legacy V1 format for compatibility. Additionally, the WasmManagerClient has been refactored to decouple configuration retrieval from the environment object by injecting a ConfigurationDatastore, and it now includes debug logging for script creation and build operations to improve observability.
app/fr/maif/izanami/v1 · high confidence
WASM integration refactored to support HTTP calls and Pekko migration
The WASM integration module has been refactored to migrate from Akka to Apache Pekko and Play 3, updating underlying HTTP client dependencies. This change introduces the capability for WASM scripts to make HTTP calls via a new \HttpCall\ host function, replacing the previous \proxy\_http\_call\ implementation. The integration context now explicitly depends on \ConfigurationDatastore\, \FeaturesDatastore\, and \WSClient\ rather than the global \Env\, improving dependency injection and testability.
app/fr/maif/izanami/wasm · high confidence
Test coverage
Added Playwright tests for frontend audit, import/export, OIDC, protected contexts, and tokens; Added comprehensive test suites for Izanami API features; Added test resources for script features and updated test logging configuration; Expanded screenshot test coverage and Playwright test stability improvements.
Dependencies
Major dependency upgrades across backend and frontend
The backend build (build.sbt) migrates from Scala 2.13 to Scala 3.3.7, upgrades the Vert.x PostgreSQL client from 4.5.1 to 5.0.12, updates Flyway from 10.4.1 to 12.6.1, switches from Akka to Pekko 1.6.0, and updates several other libraries including JNA, Rhino, and Handlebars. The frontend (izanami-frontend) upgrades React from 18 to 19, React Router from 6.4.0 to 7.4.0, Vite from 2.9.9 to 6.2.3, and adds Swagger UI and CodeMirror integrations, while also regenerating the lockfile to version 3. The manual site adds swagger-ui-react.
(dependencies) · high confidence
Housekeeping
Documentation build artifacts cleared
The generated build artifacts for the Izanami documentation site (located in manual/.docusaurus) have been removed. This includes the local search index, route definitions, and metadata files produced by Docusaurus. These files are temporary and regenerated during the build process, so their removal does not affect the source documentation content.
manual/.docusaurus · 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
This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.
Score
- CAI 44 → 48 (+4.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 46 → 46 (+0.2)
- Architecture 82 → 82 (-0.1)
- Maturity 48 → 70 (+22.7)
- Readiness 41 → 53 (+12.1)
- Security 67 → 66 (-0.8)
- Accessibility 40 → 40 (-0.1)
- Performance 73 → 85 (+12.0)
Resolved (132)
- ClassTooLong: OverloadTable (izanami-frontend/src/components/OverloadTable.tsx)
- ClassTooLong: RightSelector (izanami-frontend/src/components/RightSelector.tsx)
- Critical CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- Critical CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- Critical CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- Critical CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- Critical CVE: [GHSA redacted] (manual/package-lock.json)
- Duplicated block (33 lines × 2) (app/fr/maif/izanami/datastores/PersonnalAccessTokenDatastore.scala)
- Duplicated block (34–35 lines × 2) (app/fr/maif/izanami/web/EventController.scala)
- Duplicated block (41 lines × 2) (app/fr/maif/izanami/web/EventController.scala)
- FileTooLong: components/FeatureContexts.tsx (izanami-frontend/src/components/FeatureContexts.tsx)
- FileTooLong: pages/users.tsx (izanami-frontend/src/pages/users.tsx)
- FixmeComment (app/fr/maif/izanami/datastores/PersonnalAccessTokenDatastore.scala)
- FunctionTooLong: ConditionInput.HourRanges (izanami-frontend/src/components/ConditionInput.tsx)
- FunctionTooLong: RightTable.RightTable (izanami-frontend/src/components/RightTable.tsx)
- FunctionTooLong: wasmScripts.WasmScripts (izanami-frontend/src/pages/wasmScripts.tsx)
- Further sole-owners (lower concentration)
- High CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- High CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- High CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- …and 112 more
New (64)
- ClassTooLong: FeatureController (app/fr/maif/izanami/web/FeatureController.scala)
- ClassTooLong: LoginController (app/fr/maif/izanami/web/LoginController.scala)
- Classify ADR enforcement: 8443.c3ce8a7e.js.LICENSE (docs/assets/js/8443.c3ce8a7e.js.LICENSE.txt)
- Dependency hygiene PARTLY measured — sbt declarations read, dependency currency not (Maven Central unreachable)
- Documentation: no build, run or usage example (README.md)
- Duplicated block (36 lines × 2) (app/fr/maif/izanami/web/EventController.scala)
- Duplicated block (42–44 lines × 2) (app/fr/maif/izanami/web/EventController.scala)
- Duplicated block (6 lines × 2) (app/fr/maif/izanami/web/EventController.scala)
- FeatureTable.OverloadDetails (cyclomatic 18) (izanami-frontend/src/components/FeatureTable.tsx)
- FileTooLong: env/postgresql.scala (app/fr/maif/izanami/env/postgresql.scala)
- High CVE: [GHSA redacted] (manual/package-lock.json)
- High CVE: [GHSA redacted] (manual/package-lock.json)
- High CVE: [GHSA redacted] (manual/package-lock.json)
- High CVE: [GHSA redacted] (manual/package-lock.json)
- High CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- High CVE: [GHSA redacted] (manual/package-lock.json)
- High CVE: [GHSA redacted] (izanami-frontend/package-lock.json)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- …and 44 more
Changes since last survey
- 46 commits — 37 feature/other, 9 fixes
By area
- (root) — 8 commits
- izanami-frontend/src — 7 commits
- app/fr — 6 commits
- izanami-frontend/package-lock.json — 6 commits
- docs/v1 — 5 commits
- .github/workflows — 4 commits
- .github/dependabot.yml — 2 commits
- izanami-frontend/tests — 2 commits
- .github/scala-steward.conf — 1 commit
- izanami-frontend/.eslintrc.json — 1 commit
- izanami-frontend/.husky — 1 commit
- izanami-frontend/playwright.config.ts — 1 commit
- manual/docs — 1 commit
- manual/package-lock.json — 1 commit
Notable commits
- fix: chore: fix frontend action
- fix: chore: fix frontend prepare
- fix: fix: TS
- fix: fix: TS issues
- fix: fix: context evaluation order
- fix: fix: frontend tests
- fix: fix: impossible overload creation for project admin on global protected context
- fix: fix: modal text color regression
- fix: fix: playwright test scope
- change: Feat: user groups
- change: Setting version to 2.28.0
- change: Setting version to 2.28.1-SNAPSHOT
- change: Setting version to 2.29.0
- change: Setting version to 2.29.1-SNAPSHOT
- change: Update HikariCP to 7.1.0
- change: Update dev documentation
- change: Update dev documentation
- change: Update dev documentation
- change: Update dev documentation
- change: Update dev documentation
- …and 26 more
Architecture
- Unchanged — 0 containers · 1 contexts · 0 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
MAIF/izanami 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 7 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 81dbca8f6983dc911644696f596c843e7ef62c39 — the exact code this score is about.
- Scored under rubric-2026.11.2 — 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.3+preprod-5f8314471808.