Skip to content
CAI
Software that uses CAICheck a score

guardian/riff-raff

45.4

Weak · 6 November 2026

18k

lines of production code

Scala

with JavaScript

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add API key management interface

Users can now create, view, and delete API keys through the web interface. A new list page displays existing keys with details such as creation date, issuer, associated application, usage statistics, and last used time, while a dedicated form allows creating new keys for specific applications, including CSRF protection for security.

riff-raff/app/views/api · high confidence

Add UI for managing deployment restrictions

Users can now create, view, and manage restrictions that prevent undesirable deploys. The new Restrictions page lists existing rules, showing project name, stage, and edit-lock status, while the creation form allows specifying a project, stage (with regex support), an allowlist of email addresses for exceptions, and an option to permit continuous or scheduled deployments. A note field lets administrators explain the restriction to users attempting to deploy.

riff-raff/app/views/restrictions · high confidence

Add ability to shut down or terminate Riff-Raff instances when inactive

Riff-Raff now supports automatic shutdown or EC2 instance termination when no deployments are running, facilitated by new \ShutdownWhenInactive\ and \TerminateInstanceWhenInactive\ components in the lifecycle package. When enabled via a switch, the system waits for all active builds to complete before executing the action; the shutdown mode exits the JVM process, while the termination mode sends an Anghammarad notification via Hangouts Chat (with error logging fallback) and directly terminates the current EC2 instance to allow the Auto Scaling Group to launch a replacement.

riff-raff/app/lifecycle · high confidence

Add schedule configuration UI with timezone support

Users can now create, view, and manage scheduled deployments through a new web interface. The schedule form allows specifying a project, stage, Quartz cron expression, and a specific timezone for the schedule, along with an enabled/disabled toggle. The list view displays all configured schedules, showing the associated timezone alongside the cron expression, and provides options to edit or delete existing configurations.

riff-raff/app/views/schedule · high confidence

Add web interface for managing post-deploy hooks

Users can now create, view, edit, and delete post-deploy hooks via a new web GUI. The interface includes a form for configuring hook details such as project, stage, target URL, HTTP method, and an optional templated POST body, along with a list view that displays existing hooks and their enabled status. The form supports autocomplete for project names and displays available template tokens for dynamic content substitution.

riff-raff/app/views/hooks · high confidence

Added D3.js v2.10.3 library

The D3.js visualization library (version 2.10.3) has been added to the public JavaScript assets, including both the full source file (d3.v2.js) and its minified counterpart (d3.v2.min.js). This enables the application to use D3's data-driven document manipulation, charting, and animation capabilities.

riff-raff/public/javascripts · high confidence

Automated instance rotation and self-deployment for riff-raff

The riff-raff service now supports automatic instance rotation via a scheduled systemd timer (Wed/Thu at 08:00 London time) that triggers a rotation endpoint, and self-deployment via riff-raff.yaml which handles its own updates and AMI parameter configuration. The bootstrap script installs the service, manages configuration from S3, and ensures the rotation timer is active.

riff-raff · high confidence

Automated nightly tagging of old S3 artifacts

A new ArtifactHousekeeping component has been added to automatically tag S3 objects older than a configured number of days. The process runs nightly (defaulting to 2am) and identifies builds to retain by scanning only completed deploys for each project. It then applies a configurable tag to the corresponding S3 objects, with the feature controlled by an enabled flag in the configuration.

riff-raff/app/housekeeping · high confidence

Initial UI shell with custom error pages and versioned assets

This change introduces the foundational view templates for the Riff-Raff application, including a main page layout, authentication-aware and public entry points, and a home page that displays documentation. It adds custom error handling views that display exception details and stack traces to users, and implements asset versioning (via \Assets.versioned\) for CSS and JavaScript files to prevent browser caching issues. The layout also displays the application version and start time in the footer.

riff-raff/app/views · high confidence

Initial release of Riff-Raff configuration and routing

This change introduces the foundational configuration and routing structure for the Riff-Raff application. It adds the main Play application configuration (application.conf) defining the app name, Google OpenID authentication settings, PostgreSQL database connection, and evolution settings. It also includes Logback logging configurations for both development and production environments, and establishes the complete set of HTTP routes for the application, covering deployment requests, history, continuous deployment, hooks, restrictions, schedules, API endpoints, and management actions.

riff-raff/conf · high confidence

Initial release of Riff-Raff deployment management application

This change introduces the core Riff-Raff application, providing a web-based interface for managing software deployments. It includes controllers for initiating and tracking deploys, viewing deployment history, and managing configuration for continuous deployment, scheduled deploys, post-deploy hooks, and deployment restrictions. The application features user authentication via Google, an API for programmatic access, and a preview capability to validate deployment configurations before execution.

riff-raff/app/controllers · high confidence

Introduce deploy restrictions with allowlists and continuous deployment controls

Users can now configure restrictions to prevent undesirable deploys by specifying allowed user allowlists and controlling whether continuous deployment is permitted for specific projects and stages. The system supports stage matching via regex or literal strings, allows locking configuration editing to the original author (with optional superuser overrides), and enables scheduled deploys when continuous deployment is explicitly enabled.

riff-raff/app/restrictions · high confidence

Introduce new task infrastructure and deployment types for AWS, Fastly, and CloudFormation

The \magenta-lib/src/main/scala/magenta/tasks\ package has been restructured to support a new task-based execution model. This includes new deployment capabilities for Fastly Compute@Edge and standard Fastly VCL updates, as well as enhanced CloudFormation deployments using change sets (allowing AMI parameter updates and stack creation by tags). Autoscaling group deployments now feature robust stabilization checks, instance protection, and capacity validation. Additionally, the S3 upload task has been updated to support public read ACLs, lifecycle rules, and streaming transfers to avoid memory buffering. Also in this area: CloudFormation stack policies now protect Target Groups and use region-aware resource lists; New centralized configuration and AWS credential management; New S3-based CI build polling and continuous deployment architecture; New notification and post-deploy hook infrastructure; Introduces a new internal graph library for managing deployment task execution; and 9 more.

repository · high confidence

Introduce scheduled deployments with failure notifications

Users can now configure cron-based scheduled deploys for specific projects and stages. The system enforces safety by only triggering a scheduled deploy if the previous deployment completed successfully (skipping if the last deploy was partial, failed, or waiting) and sends notifications to teams via Anghammarad when a scheduled deploy fails to start. Scheduled deploys use the 'MostlyHarmless' update strategy and respect the timezone specified in the schedule configuration.

riff-raff/app/schedule · high confidence

New HTML helper utilities for deployment status, previews, and tooltips

Added three new helper components in the views layer to improve the deployment UI: MessageHelper provides methods to map deployment states to CSS classes and extract message types for display; PreviewHelper exposes graph dependency information to support preview capabilities for YAML configurations; and htmlTooltip offers a reusable template for rendering conditional HTML tooltips with configurable placement.

riff-raff/app/views/html · high confidence

New UI snippets for change freeze warnings, deployment history, and reporting

This change introduces a set of new view snippets in the \riff-raff/app/views/snippets\ directory to enhance the web interface. A \changeFreezeDialog\ snippet now displays a modal warning users when a change freeze is active, allowing them to proceed with deployment if necessary. The \recordTable\ snippet provides a comprehensive history view of deployments, showing details like time, deployer, stage, build ID, branch, and status (including running, completed, failed, or waiting states), with support for pagination and filtering by stage, project, status, or deployer. Additional snippets include \deploymentInstance\ for displaying deployment keys and regions, \pimpedBuildId\ for showing build metadata in tooltips, \reportTree\ for visualizing deployment report hierarchies, \pagination\ for navigating history pages, \optionalLink\ for conditional links, \inputHidden\ for form fields, and \tabbable\ for tabbed content. These components collectively improve the visibility and usability of deployment history and change management features.

riff-raff/app/views/snippets · high confidence

New configuration validation UI

Added a new web interface for validating Riff-Raff configuration files. Users can now paste YAML content into a form to check for errors, which are displayed in a structured error panel if validation fails. If the configuration is valid, the system displays a success message along with a detailed breakdown of the parsed deployments, including their type, actions, stacks, regions, app name, content directory, parameters, and dependencies.

riff-raff/app/views/validation · high confidence

New deploy target selection and redeployment UI views

Added four new Play framework views in the deployTarget area to guide users through the deployment workflow. The 'selectTarget' view allows users to choose a specific project when multiple builds match a region/stack/app combination. The 'selectVersion' view presents a list of recent deployment records for a chosen project and stage, enabling redeployment via a 'Redeploy' button. If no matching build is found, the 'noMatchForTarget' view informs the user and suggests triggering a new CI build. These views collectively provide the interface for resolving ambiguous deploy targets and initiating redeployments.

riff-raff/app/views/deployTarget · high confidence

New developer scripts for setup, starting, and testing

Added three new shell scripts to streamline local development: \script/setup\ downloads the DEV configuration from an AWS S3 bucket into \\~/.gu/riff-raff.conf\; \script/start\ launches the Docker Compose environment and runs the application via SBT, supporting a \--debug\ flag to enable JVM debugging on port 9999; and \script/test\ performs the same Docker setup but runs the test suite via SBT, also supporting the \--debug\ flag for debugging tests.

script · high confidence

New login and user profile views with Google authentication

The application now provides dedicated login and profile pages for users authenticating via Google. The login view displays a button to initiate the Google login flow and shows error messages if authentication fails. The profile view displays the user's name, email, Google subject ID, and token expiry time, along with a table of their recent deployment records.

riff-raff/app/views/auth · high confidence

New utility classes for change freezes, deployment graphs, and HSTS security

This change introduces several new utility components in the application's utils package. A ChangeFreeze utility allows administrators to restrict deployments during specific time windows and for specific stages. Graph utilities provide logic to zero-fill missing days in deployment data series for accurate time-series visualization. An HSTS filter is added to enforce secure transport headers. Additionally, new utilities include a retry mechanism for robust operations, a scheduled agent for periodic background tasks, VCS info normalization for GitHub URLs, and date formatting utilities that consistently display timestamps in London time.

riff-raff/app/utils · high confidence

Project initialization and local development environment setup

The repository has been initialized with the Riff-Raff deployment platform, replacing legacy configuration files with modern tooling. A new CONTRIBUTING.md provides instructions for running the application locally via dev containers or host laptops, including credential setup and debugging. Local dependencies are managed through .tool-versions (Java 21, SBT 1, Node 24) and docker-compose.yml, which provisions a PostgreSQL 18 database and a local DynamoDB instance with pre-created tables for development. The project is licensed under Apache 2.0, and build options are configured in .jvmopts and .sbtopts.

(repo-wide) · high confidence

YAML configuration preview with selective task deployment

Users can now preview the deployment tasks generated from a riff-raff.yaml configuration file and selectively choose which specific deployment tasks to include in a deployment. The new preview interface displays project, build, and stage details, allows users to select or deselect individual tasks via checkboxes, and shows task dependencies. A 'Deploy' button executes only the selected tasks, while a 'Preview with selections' button allows further refinement. The interface includes auto-refresh capabilities, loading states, and error handling during task resolution.

riff-raff/app/views/preview · high confidence

Removals

Removal of legacy deployment infrastructure and bundled CLI parser

The deployment tooling in src/main has been significantly simplified by removing the entire com.gu.deploy package (including ArtifactChecker, Config, Host, and Utils) and the com.gu.deploy2 package (including Install, JsonInputFile, Package, Recipe, and Resolver). Additionally, the bundled org.fud.optparse command-line argument parser has been deleted. These changes remove the previous logic for checking approved build statuses, parsing command-line arguments via the FUD library, and resolving JSON-based installation recipes, indicating a shift away from the prior deployment workflow.

src/main · high confidence

Behavioural changes

13 commits (2 fixes) modifying riff-raff/app/deployment/preview

A change to existing behaviour in riff-raff/app/deployment/preview — 13 commits (2 fixs), 1 file: “Stream the S3 copy rather than buffer entirely”; “Revert "Exceptions =\> Error values"”; “Project compiles”; and 10 more.

riff-raff/app/deployment/preview · medium confidence · unverified

173 commits (16 fixes) modifying magenta-lib/src/main/scala/magenta/deployment\_type

A change to existing behaviour in magenta-lib/src/main/scala/magenta/deployment\_type — 173 commits (16 fixs), 11 files: “Initial commit of rehashed logging without thread local vars”; “Further improve parameter validation”; “Add VCS URL tag to Cloudformation stacks on update”; and 167 more (refs \#504, \#520, \#521, \#292, \#619, …).

_magenta-lib/src/main/scala/magenta/deployment\type · medium confidence · unverified

18 commits (0 fixes) modifying magenta-lib/src/main/scala/magenta/input

A change to existing behaviour in magenta-lib/src/main/scala/magenta/input — 18 commits, 2 files: “Implement core deployment type and task for updating GCP deploys”; “When parsing the YAML check for extra fields”; “Upgrade to Play 2.6”; and 15 more (refs \#633).

magenta-lib/src/main/scala/magenta/input · medium confidence · unverified

4 commits (0 fixes) modifying magenta-lib/src/main/scala/magenta/tasks/stackSetPolicy

A change to existing behaviour in magenta-lib/src/main/scala/magenta/tasks/stackSetPolicy — 4 commits, 1 file: “correct the sbt task name in the comments”; “add cache generator for cfn types list”; “scalafmt”; and 1 more.

magenta-lib/src/main/scala/magenta/tasks/stackSetPolicy · medium confidence · unverified

4 commits (0 fixes) modifying riff-raff/app/docs

A change to existing behaviour in riff-raff/app/docs — 4 commits, 1 file: “Change home page to display documentation index”; “Introduce scalafmt”; “Remove some left over logging”; and 1 more.

riff-raff/app/docs · medium confidence · unverified

42 commits (3 fixes) modifying riff-raff/app/deployment

A change to existing behaviour in riff-raff/app/deployment — 42 commits (3 fixs), 2 files: “Yep, that should have been min”; “Initial commit of rehashed logging without thread local vars”; “Catch and log any exceptions thrown by the update method”; and 39 more.

riff-raff/app/deployment · medium confidence · unverified

42 commits (5 fixes) modifying magenta-lib/src/main/scala/magenta

A change to existing behaviour in magenta-lib/src/main/scala/magenta — 42 commits (5 fixs), 3 files: “I must never use a default parameter for a critical flag”; “Add some debug and warnings around the S3 upload task”; “Further renaming”; and 38 more (refs \#677).

magenta-lib/src/main/scala/magenta · medium confidence · unverified

46 commits (6 fixes) modifying riff-raff/app/notification

A change to existing behaviour in riff-raff/app/notification — 46 commits (6 fixs), 3 files: “Simplify getTargets function”; “Use Class instead of an Object to avoid passing prefix around so much”; “fix: Use raw YAML to determine Anghammarad targets”; and 43 more (refs \#1433, \#535, \#1571, \#702).

riff-raff/app/notification · medium confidence · unverified

59 commits (12 fixes) modifying magenta-lib/src/main/scala/magenta/tasks

A change to existing behaviour in magenta-lib/src/main/scala/magenta/tasks — 59 commits (12 fixs), 3 files: “Initial commit of rehashed logging without thread local vars”; “refactor: Simplify logging”; “feat(cloud-formation): Preserve existing tags”; and 55 more (refs \#519, \#504, \#1542).

magenta-lib/src/main/scala/magenta/tasks · medium confidence · unverified

6 commits (0 fixes) modifying riff-raff/app/resources

A change to existing behaviour in riff-raff/app/resources — 6 commits, 1 file: “Introduce scalafmt”; “URL encode parameter values”; “Further modifications to Riff-Raff to lookup instances via Prism”; and 3 more.

riff-raff/app/resources · medium confidence · unverified

7 commits (1 fix) modifying magenta-lib/src/main/scala/magenta/graph

A change to existing behaviour in magenta-lib/src/main/scala/magenta/graph — 7 commits (1 fix), 1 file: “Implement own simple graph and switch to 'Deployments' for nodes”; “Introduce scalafmt”; “Make graph implementation generic and add new methods”; and 4 more.

magenta-lib/src/main/scala/magenta/graph · medium confidence · unverified

79 commits (9 fixes) modifying riff-raff/app/ci

A change to existing behaviour in riff-raff/app/ci — 79 commits (9 fixs), 9 files: “Separate polling for jobs from polling for builds”; “Oh, ExecutionContext, we meet again”; “Add VCS URL tag to Cloudformation stacks on update”; and 73 more (refs \#535).

riff-raff/app/ci · medium confidence · unverified

Database schema evolution and read-only access setup

This change introduces a series of database evolutions that establish the core RiffRaff schema (apiKey, auth, deploy, deployLog) and optimize query performance by adding specific indexes on JSONB fields such as application, startTime, status, and projectName. It also creates a read-only \service\_catalogue\ user and schema with views exposing deploy and deploy log data for external consumption, while subsequently removing the \auth\ table and its associated view to align with updated authentication requirements.

riff-raff/conf/evolutions · high confidence

Migrate application startup to Play 2.6 ApplicationLoader architecture

The application now uses the Play 2.6+ ApplicationLoader pattern (AppLoader and AppComponents) instead of the legacy GlobalSettings approach. This change centralizes dependency injection and configuration, enabling features such as CSRF protection, Gzip filtering, and secret rotation via AWS Systems Manager Parameter Store. It also integrates IAM-based database password retrieval and configures the deployment engine with the available deployment types.

riff-raff/app · high confidence

Migrate configuration and metadata storage to DynamoDB and introduce dynamic database authentication

Riff-Raff now stores continuous deployment configurations, post-deploy hook settings, scheduled deploy configurations, and deployment restrictions in DynamoDB tables (using the Scanamo library) instead of the previous storage mechanism. Additionally, the system supports dynamic database password generation via IAM authentication for PostgreSQL connections, allowing secure, rotating credentials in production environments while falling back to static passwords in non-production stages.

riff-raff/app/persistence · high confidence

New Continuous Deployment configuration UI with change freeze support

The Continuous Deployment configuration interface has been replaced with new views that allow users to create, edit, and delete deployment configurations via a form (selecting project, stage, branch, and trigger) and a list view. The list view now displays a warning banner when a change freeze is active, disabling deploys for affected stages, and highlights disabled configurations. All forms include CSRF protection to secure POST requests.

riff-raff/app/views/continuousDeployment · high confidence

New centralized configuration and AWS credential management

The application now uses a new \Config\ class in the \conf\ package to manage settings, replacing previous property-file approaches. This change introduces support for AWS SSM Parameter Store to dynamically load credentials based on service and account keys, and adds configuration sections for authentication (including Google OAuth domains and superusers), continuous deployment toggles, change freezes, and housekeeping schedules. The system also auto-detects the deployment stage via EC2 instance tags and configures AWS clients (S3, DynamoDB, SNS, SSM) with region-specific settings, defaulting to \eu-west-1\.

riff-raff/app/conf · high confidence

New documentation page templates and components

The documentation UI now uses new Play framework view templates to render content more consistently. A breadcrumb component displays navigation paths, while a dedicated template for deployment types renders action and parameter tables with their documentation and defaults. Markdown pages now include previous/next navigation links, and multi-section documentation pages use Bootstrap nav-pills for section navigation.

riff-raff/app/views/documentation · high confidence

New form definitions for deployment, migration, and UUID-based actions

The application introduces three new form models to handle specific user inputs: DeployParameterForm now captures deployment details including an update strategy, selected keys, and total key count; MigrationParameters defines a form for limit and action inputs with query string binding support; and UuidForm validates a fixed-length UUID string alongside an action. These forms standardize input validation and mapping for their respective features.

riff-raff/app/controllers/forms · high confidence

New styling for deployment graphs and magenta theme components

This change introduces new stylesheets for the application's UI. The \graph.less\ file defines the layout and appearance of the deployment history graphs (powered by Rickshaw), including specific styles for dark mode support via \prefers-color-scheme\. The \magenta.less\ file establishes the visual theme for the 'magenta' interface, defining styles for table rows, tooltips, command output messages, and status indicators (such as the 'party parrot' animation for running states and green checkmarks for completed ones).

riff-raff/app/assets/stylesheets · high confidence

Redesigned deployment form with project favorites and enhanced interaction

The deployment interface now supports saving and selecting favorite projects via a new favorites list, with duplicate prevention and empty-input protection. Project selection uses exact matching, and switching projects automatically clears the build and branch inputs while refreshing stage and deploy information. The form now includes a timezone selector for cron expressions, a collapsible deploy log, and a mini history pane for contextual deployment history. Desktop notifications are enabled for ongoing deployments, and a warning appears when deploying non-standard branches to production. Additional improvements include CSRF handling for the stop-deploy button, preserved expand/collapse states across auto-refreshes, and basic Mixpanel tracking for verbose mode toggles.

riff-raff/app/assets/javascripts · high confidence

Redesigned deployment interface with dashboard, history, and artifact browsing

The deployment user interface has been significantly restructured and expanded. A new Dashboard view provides an auto-refreshing, AJAX-driven overview of recent deployments across projects and stages. The Deployment History page now features a visual graph of deploy activity, along with robust filtering by stage, status, and project, as well as pagination. The main Deploy form has been enhanced with project auto-suggest, a favorites list, and an expandable section for advanced update strategies. Additionally, users can now view detailed build information (including branch, tags, and CI status) and browse the contents of artifact files directly from the deployment view.

riff-raff/app/views/deploy · high confidence

Redesigned navigation bar with user authentication and version display

The application's top navigation bar has been restructured to include a brand link displaying the current build version and start time, alongside a user-specific menu. When a user is logged in via Google authentication, a dropdown appears showing their name with links to their profile and a sign-out option; unauthenticated users see a login link instead. The menu items themselves now support both standard links and dropdown sub-menus, with visibility and active states determined by the current request context.

riff-raff/app/views/menu · high confidence

Refactored deployment resolution into a modular graph-based pipeline

The deployment resolution logic in the input resolver has been restructured from a monolithic approach into a series of specialized components that build and process a dependency graph. This change introduces distinct stages for resolving configuration (DeploymentResolver), validating deployment types and parameters (DeploymentTypeResolver), pruning deployments based on user selectors (DeploymentPruner), and constructing the execution graph (DeploymentGraphBuilder, DeploymentGraphActionFlattening). The main Resolver orchestrates these steps, allowing for more granular validation, support for partial deployment selection (by stack, region, or specific keys), and the flattening of multi-action deployments into individual graph nodes for parallel execution.

magenta-lib/src/main/scala/magenta/input/resolver · high confidence

Updated UI theme to Slate

The application's visual appearance has been updated by switching the Bootstrap CSS theme to Slate. This change replaces the previous stylesheet with the Slate variant from Bootswatch (based on Bootstrap v3.4.1), resulting in a darker color scheme for backgrounds, text, and interface elements.

riff-raff/public/stylesheets · high confidence

Test coverage

10 commits adding/updating tests in riff-raff/test/docs; Add new testing and debugging utility pages; Added integration tests for the Postgres datastore; Added test coverage for deployment types and reporting infrastructure; Added test fixtures for deployment graph and context creation; Added tests for PrismLookup and Keyring functionality; Added tests for VCS URL normalization, graph zero-filling, and message helper; Added tests for deployment failure notifications and webhook templating; Added tests for deployment record mapping and log document tree utilities; Added tests for restriction checker logic; Added tests for scheduled deploy job validation logic; Added tests for the deployment preview functionality; Added unit tests for ArtifactHousekeeping logic; Added unit tests for CI integration components; Added unit tests for deployment actor coordination and execution; Removal of obsolete test files in src/test.

Dependencies

Upgrade to Play 3 and AWS SDK v2

The build configuration has been upgraded to Play 3.0.11 (via the sbt-plugin) and the AWS SDK for Java v2 (version 2.52.1). This migration updates core dependencies including \play-googleauth\ and \play-secret-rotation\ to their Play 3-compatible versions, replaces legacy AWS SDK v1 libraries with the v2 equivalents (e.g., \software.amazon.awssdk\), and updates the SBT version to 1.13.0. Additionally, a new \GenerateCfnTypes\ tool has been added to the build process to cache AWS CloudFormation types, and \logback-classic\ is pinned to 1.6.3 to address [CVE redacted].

project · high confidence

Upgrade to Scala 2.13.18 and Netty 4.2.18.Final

The build configuration has been updated to use Scala 2.13.18 and the Netty HTTP codec library version 4.2.18.Final. Additionally, the project now targets Java 21, requiring specific JVM flags to open internal modules for legacy reflection usage, and configures Docker Compose to manage test container lifecycles.

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

Lenses

  • Code Health 52 → 52 (+0.0)
  • Architecture 85 → 85 (+0.0)
  • Maturity 35 → 58 (+23.7)
  • Readiness 63 → 48 (-14.9)
  • Security 81 → 74 (-6.4)
  • Accessibility 33 → 33 (+0.0)
  • Performance 100 → 100 (+0.0)

Resolved (34)

  • Off-boarding risk: anonymized user #1
  • Outdated: ch.qos.logback:logback-classic
  • Outdated: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml
  • Outdated: com.fasterxml.jackson.module:jackson-module-scala_2.13
  • Outdated: com.gu.play-googleauth:play-v30_2.13
  • Outdated: com.gu.play-secret-rotation:aws-parameterstore-sdk-v2_2.13
  • Outdated: com.gu.play-secret-rotation:play-v30_2.13
  • Outdated: com.squareup.okhttp3:okhttp
  • Outdated: io.netty:netty-codec-http
  • Outdated: joda-time:joda-time
  • Outdated: net.logstash.logback:logstash-logback-encoder
  • Outdated: org.postgresql:postgresql
  • Outdated: org.scalikejdbc:scalikejdbc_2.13
  • Outdated: org.webjars:bootstrap
  • Outdated: org.webjars:jquery
  • Outdated: org.webjars:webjars-play_2.13
  • Outdated: software.amazon.awssdk:autoscaling
  • Outdated: software.amazon.awssdk:cloudformation
  • Outdated: software.amazon.awssdk:core
  • Outdated: software.amazon.awssdk:dynamodb
  • …and 14 more

New (3)

  • Dependency hygiene PARTLY measured — sbt declarations read, dependency currency not (Maven Central unreachable)
  • Off-boarding risk: anonymized user #1
  • d3.v2.d3.format.<returned closure> (cognitive 16) (riff-raff/public/javascripts/d3.v2.js)

Changes since last survey

  • 5 commits — 5 feature/other, 0 fixes

By area

  • (repo) — 2 commits
  • (root) — 1 commit
  • project/Dependencies.scala — 1 commit
  • project/plugins.sbt — 1 commit

Notable commits

  • change: Merge pull request #1665 from guardian/akash1810-patch-2
  • change: Merge pull request #1666 from guardian/ash/vulnerabilities
  • change: Update devenv to 20260930-111347 (#1664)
  • change: chore(deps): Update Play Framework sbt plugin version to 3.0.12
  • change: chore: Update fastly-api-client

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

guardian/riff-raff 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 6 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 7bf91091ede28a55e3bcdd930130527d6067cb72 — 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-60d1b390edf0.