Skip to content
CAI
Software that uses CAICheck a score

bravodev-hub/appointme

55.2

Adequate · 8 November 2026

20.1k

lines of production code

TypeScript

with C#

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Cloudflare Worker proxy enables custom domain on Free tier

A new Cloudflare Worker has been added to route traffic from app.appointme.dev to the Azure App Service origin. This proxy allows the application to use a custom hostname despite the Azure Free (F1) tier restriction on custom bindings, by terminating TLS at Cloudflare and forwarding requests with the original host header.

infra/cloudflare-worker · high confidence

Dashboard statistics and peak hours endpoints with demo data seeding

This change introduces the backend components for the Booking dashboard, including endpoints to retrieve aggregated appointment statistics (total appointments, utilization, returning client rate, staff load, and trend buckets) and peak-hour analysis, along with the underlying calculators and database queries that filter for active providers and respect company time zones. It also adds a recurring job that seeds demo appointments daily to support dashboard visualization in demo environments, and introduces rowversion concurrency tokens on the Appointment, Attendee, BookingCompany, and ServiceProvider entities to prevent lost updates during concurrent modifications.

src/Booking · high confidence

New dashboard with business statistics and customer management actions

Users can now access a new Dashboard page that displays key performance indicators (appointments, revenue, chair utilization, returning clients) with period-over-period comparisons, alongside trend charts, peak-hour heatmaps, and staff load views. Revenue figures are currently derived from deterministic fake data based on appointment counts. Additionally, customer and team management actions (edit, delete, manage roles, resend/cancel invitations) are now available via dropdown menus in their respective lists, gated by specific permissions like customers:update, customers:delete, and employees:update\_roles.

src/AppointMe.Frontend/src/app · high confidence

Security

CSRF protection for logout and API requests

The application now includes CSRF protection for the logout flow and general API interactions. The logout function has been updated to submit a POST request via a dynamically created form instead of a simple GET, mitigating logout CSRF attacks. Additionally, the Axios HTTP client instance is configured to automatically handle XSRF tokens using the 'XSRF-TOKEN' cookie and 'X-XSRF-TOKEN' header, ensuring subsequent API requests are protected against cross-site request forgery.

src/AppointMe.Frontend/src/lib · high confidence

Behavioural changes

1 commit (0 fixes) modifying src/AppointMe.Api/DataProtection, src/AppointMe.Shared/Configuration

A change to existing behaviour in src/AppointMe.Api/DataProtection, src/AppointMe.Shared/Configuration — 1 commit, 2 files: “- add demo login for live demo and local quick start - seed KC demo user via realm import file - switch to npm instead of yarn for frontend build”.

src/AppointMe.Api/DataProtection, src/AppointMe.Shared/Configuration · medium confidence · unverified

1 commit (0 fixes) modifying src/AppointMe.Shared/Authentication

A change to existing behaviour in src/AppointMe.Shared/Authentication — 1 commit, 2 files: “Add administration menu”.

src/AppointMe.Shared/Authentication · medium confidence · unverified

1 commit (0 fixes) modifying src/AppointMe.Shared/Companies

A change to existing behaviour in src/AppointMe.Shared/Companies — 1 commit, 3 files: “Seed data job for dashboard”.

src/AppointMe.Shared/Companies · medium confidence · unverified

1 commit (0 fixes) modifying src/AppointMe.Shared/Domain

A change to existing behaviour in src/AppointMe.Shared/Domain — 1 commit, 2 files: “Dashboard”.

src/AppointMe.Shared/Domain · medium confidence · unverified

5 commits (1 fix) modifying src/AppointMe.Frontend/src

A change to existing behaviour in src/AppointMe.Frontend/src — 5 commits (1 fix), 20 files: “Wait for a stored company before rendering company-scoped UI”; “Fix optional pagination params and 500s on request binding errors”; “Migrate data tables to TanStack Table 9”; and 2 more. Also in this area: Frontend toolchain migration to Vite+ with unified linting and formatting.

src/AppointMe.Api/Wolverine, src/AppointMe.Frontend/src/api · medium confidence · unverified

52 commits (9 fixes) modifying (repo-wide)

A change to existing behaviour in (repo-wide) — 52 commits (9 fixs), 10 files: “docs: reference identity resolution deep dive from README”; “Document the template install path and fix the repository URL”; “Add nuget.org package README; bump template to 1.2.1”; and 45 more.

(repo-wide) · low confidence · unverified

Constrain system role assignments and add row version concurrency

Assigning or removing system roles (such as Owner or Manager) now requires the managing user to hold the new 'manage\_owners' permission; attempts without this permission will fail with a validation error. Additionally, row version concurrency tokens have been added to the Company, Employee, EmployeeInvitation, and RolePermissionOverride database tables to prevent data conflicts during concurrent updates.

src/Organizations · high confidence

Demo login support and session security hardening

The API now includes a /login/demo endpoint that allows pre-provisioned users to sign in directly via the backend, supporting both Keycloak (ROPC) and Microsoft Entra External ID (native auth) identity providers for quick local or demo access. Session management has been hardened by explicitly setting a 7-day expiration with sliding expiration, and the authentication cookie now stores only the ID token (removing access/refresh tokens) to prevent header size limits and improve security. Additionally, the default for RequireHttpsMetadata has been changed to true to enforce HTTPS for identity provider metadata fetching in production environments.

src/AppointMe.Api/Authentication · high confidence

Demo seeding saga updated with higher customer count and simplified tenant binding

The demo seeding process now generates 400 customers instead of 100, providing a more populated environment for testing. Additionally, the saga's command construction has been simplified by replacing the string-based tenant ID assignment with a direct company ID binding, streamlining how the demo data is associated with the company context.

src/AppointMe.Api/Demo · high confidence

Demo user seeding and frontend build tooling update

The local development environment now includes a pre-seeded demo user ([e-mail redacted]) in the Keycloak realm configuration, allowing immediate access to the application without manual registration. Additionally, the frontend build process has switched from Yarn to npm, requiring npm for local development, and the Keycloak client configuration now enables direct access grants to support this demo flow. Also in this area: 7 commits (1 fix) modifying src/AppointMe.Frontend; Enforce HTTPS development certificate trust at startup.

src/AppointMe.Aspire · medium confidence · unverified

Devtest infrastructure cost controls and Service Bus removal

The devtest environment now removes the Azure Service Bus module entirely, with the App Service module no longer accepting or injecting a Service Bus connection string. The App Service Plan default SKU has been changed from Basic (B1) to Free (F1), which disables Always On and requires a Cloudflare Worker for custom domain binding. SQL Database defaults to the Basic tier (5 DTU, 2 GB cap) instead of Standard (S0), and Log Analytics now enforces a 0.5 GB/day ingestion cap to prevent runaway costs.

infra/modules · high confidence

Enable OpenTelemetry tracing and metrics for Wolverine

The API's OpenTelemetry configuration now explicitly includes instrumentation sources and meters for Wolverine. This ensures that distributed traces and metrics generated by Wolverine are captured and exported via OTLP, providing visibility into Wolverine-related operations alongside existing ASP.NET Core, HTTP client, and SQL client telemetry.

src/AppointMe.Api/OpenTelemetry · high confidence

Enhanced security posture with CSRF protection, security headers, and HSTS

The API now enforces stricter security standards by introducing custom Antiforgery middleware that validates state-changing requests on the /api prefix while issuing tokens for authenticated sessions, and by adding a Security Headers middleware that sets X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and a Content-Security-Policy-Report-Only header. Additionally, HTTP Strict Transport Security (HSTS) is enabled for non-development environments, and data protection keys are now configurable to persist to Azure Blob Storage via a dedicated connection string. The frontend build process has also switched from Yarn to npm, and the application now honors the X-Original-Host header to correctly identify the public hostname when behind proxies like Cloudflare.

src/AppointMe.Api · high confidence

Frontend build tooling and configuration updates

The frontend build system has switched from Yarn to npm, requiring users to use npm commands for development and building. The Vite configuration now uses import.meta.dirname for path resolution, and the ESLint rules have been updated to exempt vendored shadcn/ui components from the single-export rule to support cleaner updates. Additionally, the orval code generator no longer applies prettier formatting during API client generation, relying instead on post-generation hooks, and documentation has been updated to reflect these changes along with specific instructions for managing npm lockfile compatibility. Also in this area: 7 commits (1 fix) modifying src/AppointMe.Frontend; Frontend toolchain migration to Vite+ with unified linting and formatting.

src/AppointMe.Frontend · medium confidence · unverified

Hangfire dashboard access restricted to super-admins

Access to the Hangfire job dashboard at /admin/jobs is now gated behind a new authorization policy that requires both an authenticated user and the super-admin role. This is enforced by introducing a SuperAdminRequirement and handler, registering the policy in the authorization service collection, and applying the policy to the Hangfire dashboard endpoint mapping.

src/AppointMe.Api/Authorization · high confidence

Optimistic concurrency conflict handling for appointments

The API now detects and handles optimistic concurrency conflicts when updating appointments. If a record is modified by another operation while being edited, the system returns a 409 Conflict response with a clear message instructing the user to reload and try again, preventing silent data overwrites.

src/AppointMe.Api/ErrorHandling · high confidence

Platform super-admin role, tenant-scoped messaging, and pagination limits

This update introduces a platform-level 'super admin' role (configured via email list) that operates independently of company boundaries, alongside new extension methods to seamlessly attach company context to Wolverine messages and invoke commands scoped to a specific tenant. It also adds configuration options for a demo mode with seeded user credentials, domain logic for aggregating statistics into day/week/month buckets, and a fix to prevent SQL connection leaks during open failures. Additionally, the maximum pagination limit per request is lowered from 1000 to 100 rows to reduce resource consumption. Also in this area: 4 commits (1 fix) modifying src/AppointMe.Api.

src/AppointMe.Shared/Database, src/AppointMe.Shared/Pagination · medium confidence · unverified

Refactored context hooks and improved error handling in frontend components

The auth and theme context hooks (useCurrentUser, useCurrentCompany, useUserAccess, useTheme) have been split into separate .ts files to follow fast-refresh conventions, with the context providers now importing from these new hook files. The permission system now supports checking multiple permissions at once, allowing the Can component to accept an array of permissions. Error handling in the signup and onboarding forms has been improved to properly catch and display specific error messages from the API, including better handling of Axios errors. Additionally, the modal dialog provider now uses unknown type instead of any for better type safety, and the onboarding form now includes a name attribute on the timezone select field. Also in this area: 5 commits (1 fix) modifying src/AppointMe.Frontend/src; Frontend toolchain migration to Vite+ with unified linting and formatting.

src/AppointMe.Frontend/src/components · medium confidence · unverified

Simplifies devtest infrastructure and updates deployment documentation

The devtest environment now uses a free App Service plan (F1) instead of B1, a Basic SQL tier instead of Standard (S0), and a 0.5 GB/day ingestion cap for Log Analytics. Azure Service Bus has been removed from the provisioned resources. The deployment guide has been reworked to focus on GitHub Actions with OIDC authentication, removing GitLab CI support, and adding instructions for optional custom domain binding via Cloudflare Workers.

infra · high confidence

Upgrade to React Router v8

The application has upgraded its routing library to React Router v8. This change updates the import paths for core routing components, such as moving \RouterProvider\ to \react-router/dom\ and \useBlocker\ to \react-router\, ensuring compatibility with the new major version's module structure.

src/AppointMe.Frontend/src, src/AppointMe.Frontend/src/hooks · high confidence

User logout now requires authentication and POST requests

The logout endpoint has been changed from an anonymous GET request to a POST request that requires authorization. This prevents unauthorized users from triggering logout actions and mitigates potential CSRF vulnerabilities associated with GET-based state changes. Additionally, a rowversion concurrency token has been added to the User entity to handle optimistic concurrency control in the database.

src/Identity · high confidence

Test coverage

Added template package documentation and smoke-test harness; Added unit tests for API security middleware and authorization; Added unit tests for shared domain and infrastructure components.

Dependencies

Major dependency upgrades and security hardening across frontend and backend

This update upgrades the frontend to React 19 and React Router v8, replacing the legacy react-router-dom package, and enforces Node.js 22 as the minimum runtime. The backend upgrades .NET 10 packages (including EF Core, Aspire, and Wolverine) to their latest minor versions and introduces a transitive pin for Microsoft.OpenApi to version 2.11.0 to address the [GHSA redacted] vulnerability. Additionally, the frontend has switched from Yarn to npm, removing yarn.lock in favor of a complete package-lock.json, and adds overrides for undici and minimatch to further secure the dependency tree. Also in this area: 1 commit updating dependencies (1 manifest); 13 commits updating dependencies (11 manifests); Frontend build tooling migrates from Vite to Vite+; Update dependencies and improve template packaging; AppointMe Templates package version bump to 1.2.0; and 1 more.

(dependencies) · high confidence · unverified

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 → 55 (+6.6)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 82 → 82 (-0.6)
  • Architecture 74 → 74 (-0.2)
  • Maturity 43 → 66 (+22.8)
  • Readiness 39 → 41 (+2.4)
  • Security 72 → 72 (-0.3)
  • Domain Modelling 73 → 73 (+0.0)
  • Event-Driven 100 → 100 (+0.0)
  • Accessibility 63 → 63 (+0.1)
  • Performance 72 → 77 (+5.5)

Resolved (34)

  • Documentation: no project overview (docs/superpowers/specs/2026-08-08-footer-build-version-design.md)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • High CVE: System.Security.Cryptography.Pkcs 10.0.10
  • High CVE: System.Security.Cryptography.Pkcs 10.0.11 (src/AppointMe.Aspire/AppointMe.Aspire.csproj)
  • High CVE: System.Security.Cryptography.Pkcs 9.0.18 (src/AppointMe.Api/AppointMe.Api.csproj)
  • High CVE: System.Security.Cryptography.Xml 10.0.10
  • High IaC: WD-COMPOSE-0002 (compose.yaml)
  • Identity: 2 contract type(s) expose producer-owned ids/enums
  • Inconsistent pagination and filtering strategy across rehydration sources. Customer source supports pagination/filtering, Company source returns all (no pagination), Employee source returns all for a company (no pagination). This suggests a lack of unified contract for bulk data retrieval.
  • Medium CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • Medium CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • Medium CVE: [GHSA redacted] (src/AppointMe.Frontend/package.json)
  • Medium CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • …and 14 more

New (11)

  • AppointMe.Identity: 2 contract type(s) expose producer-owned ids/enums
  • AppointMe.Organizations: 4 contract type(s) expose producer-owned ids/enums
  • FunctionTooLong: event-calendar-views.EventCalendarViews (src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx)
  • High CVE: [GHSA redacted] (src/AppointMe.Frontend/package-lock.json)
  • Medium IaC: WD-COMPOSE-0002 (compose.yaml)
  • Projects may be oversized for their cohesion (src/AppointMe.Shared/AppointMe.Shared.csproj)
  • Projects may be oversized for their cohesion (src/Booking/AppointMe.Booking/AppointMe.Booking.csproj)
  • Split AppointMe.Shared (src/AppointMe.Shared/AppointMe.Shared.csproj)
  • event-calendar-views.EventCalendarViews (cognitive 44) (src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx)
  • event-calendar-views.EventCalendarViews (cyclomatic 49) (src/AppointMe.Frontend/src/components/ui/event-calendar-views.tsx)
  • redundant comment (src/AppointMe.Frontend/src/components/ui/sidebar.tsx)

Changes since last survey

  • 21 commits — 17 feature/other, 4 fixes

By area

  • (root) — 9 commits
  • src/AppointMe.Frontend — 7 commits
  • src/AppointMe.Api — 4 commits
  • src/Identity — 1 commit

Notable commits

  • fix: Bump .NET to 10.0.14 (OOB security fix) and Wolverine to 6.60
  • fix: Bump dependencies; fix npm and NuGet security advisories
  • fix: Fix optional pagination params and 500s on request binding errors
  • fix: Migrate tests to xUnit.net v3; fix smoke-test Appointment baseline
  • change: Check Wolverine handler code generation in CI
  • change: Drop IsGeneratingOpenApiDocument; use IsRunningGeneration for Wolverine
  • change: Drop the lone [FromServices] in LoginEndpoint
  • change: Generate the OpenAPI document at build time for orval
  • change: Make generate:api build the API before running orval
  • change: Migrate data tables to TanStack Table 9
  • change: Move CI and Docker to Node 24; add Dependabot; bump local images
  • change: README: Vite 8 via Vite+ and build-time OpenAPI; Node requirement in package README
  • change: README: link the documentation at appointme.dev/docs
  • change: Regenerate the OpenAPI document when a module assembly changes
  • change: Run the API with the https launch profile in the Compose instructions
  • change: Switch to Aspire.Hosting.JavaScript; drop unused dependencies
  • change: Upgrade Recharts to 3.10 and the shadcn chart component
  • change: Upgrade temporal-polyfill 1.0, react-pacer 0.24, react-hotkeys 0.14
  • change: Upgrade the appointments calendar to FullCalendar 7
  • change: Wait for a stored company before rendering company-scoped UI
  • …and 1 more

API surface

  • Unchanged — 32 HTTP endpoints

Architecture

  • Unchanged — 4 containers · 5 contexts · 8 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

bravodev-hub/appointme 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 8 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 6a478d4d6ea8f3f7020d0dde5aace5aa99f6b37a — 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-45ab2cab63de.