Skip to content
CAI
Software that uses CAICheck a score

ossf/best-practices-badge

53.3

Adequate · 6 November 2026

24.8k

lines of production code

Ruby

primary language

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add password reset user interface

Users can now initiate and complete password resets through two new views: a form to request a reset link by entering their email address, and a form to set a new password using the received token. The interface includes standard error handling and input validation fields for password confirmation.

_app/views/password\resets · high confidence

Add security.txt and custom error pages

The application now includes a .well-known/security.txt file to provide standardized contact information for security vulnerability reporting, along with custom HTML error pages for 404 (Not Found), 422 (Unprocessable Entity), and 500 (Internal Server Error) responses to improve user experience during errors. Additionally, a Google site verification file has been added to support search engine ownership verification.

public · high confidence

Add unsubscribe page for managing notification preferences

Users can now visit a dedicated unsubscribe page to manage their notification settings. The new view presents a form where users can review their email, issue, and token details in read-only fields and submit a request to unsubscribe from notifications.

app/views/unsubscribe · high confidence

Added development environment binstubs and Solid Queue CLI

The application now includes a set of executable binstubs in the \bin/\ directory to streamline local development workflows. These include standard Rails utilities (\rails\, \rake\, \setup\, \update\, \spring\) and tooling wrappers (\brakeman\, \rubocop\, \license\_finder\, \yaml-lint\, \redcarpet\, \rails\_best\_practices\) that ensure consistent execution environments. Additionally, a new \bin/jobs\ script has been added to launch the Solid Queue background job processor, and \bin/dev\ provides a convenient entry point for starting the development server.

bin · high confidence

Admin login sessions listing view

Added a new view for the login sessions index page that displays a table of all currently active login sessions, sorted by most recently used. The table includes hyperlinked User ID and User Name columns, the user's role, IP address, user agent, creation and last-used timestamps, and a truncated session digest. The view also includes a note on how to revoke suspicious sessions via a rake task and renders pagination for large lists.

_app/views/login\sessions · high confidence

Initial internationalization support with multi-language translations

The application now supports multiple languages, introducing a locale selection feature for users. This change adds translation files for English, German, Spanish, French, Japanese, Brazilian Portuguese, Russian, Swahili, and Simplified Chinese, covering UI text, navigation, and error messages. It also includes language-specific formatting rules for dates, numbers, and currencies to ensure correct local display.

config/locales · high confidence

Initial machine-translated UI strings for German, Spanish, and French

The application now includes initial machine-translated user interface strings for German (de), Spanish (es), and French (fr). These YAML configuration files provide translations for core user flows, including project submission, badge criteria descriptions, user account management, and notification settings, enabling non-English speakers to interact with the platform's primary features.

_config/machine\translations · high confidence

Initial repository configuration and development environment setup

This change establishes the foundational configuration for the OpenSSF Best Practices Badge project, introducing essential tooling and environment definitions. It adds linter configurations for Ruby (RuboCop), JavaScript (ESLint), and Markdown (mdl), along with security audit settings (Bundler Audit) and code coverage rules (SimpleCov). The entry also defines the target runtime versions via .ruby-version (Ruby 3.4.10) and .tool-versions (Node.js 19.5.0), sets up Heroku deployment behavior through Procfile and .slugignore, and configures version control exclusions in .gitignore. Additionally, it includes project governance documents such as the Code of Conduct, Contributing guidelines, and AI assistant instructions (AGENTS.md).

(repo-wide) · high confidence

Introduce asset staleness checking and baseline criteria management infrastructure

The application now includes an \AssetStalenessChecker\ and \AssetStalenessMiddleware\ that detect when precompiled assets are out of sync with source files, failing fast in development and test environments while warning in production. Additionally, a suite of new libraries (\BaselineCriteriaValidator\, \BaselineHtmlParser\, \BaselineI18nExtractor\, \BaselineMigrationGenerator\, \CriterionStatus\) has been added to support the synchronization, validation, and migration of OpenSSF Baseline criteria, alongside \DatabaseBootRetry\ and \DatabaseUrlGuard\ to improve boot-time resilience against transient database connection issues.

lib · high confidence

Introduce mailer infrastructure with privacy-focused headers and localization

This change introduces the core mailer classes (ApplicationMailer, ReportMailer, UserMailer) that handle all system email notifications. It establishes a default sender address configurable via environment variables and implements privacy protections by disabling SendGrid click and open tracking via the X-SMTPAPI header. The mailers support internationalization, automatically using the recipient's preferred locale for subjects and content, and include specific logic for account activation delays, badge status change notifications, and user update alerts.

app/mailers · high confidence

Introduce new controllers for account activation, password resets, and session management

This change adds several new controllers to handle core user lifecycle and authentication flows. AccountActivationsController manages the activation of local user accounts with a configurable cool-off period before login is permitted. PasswordResetsController implements a privacy-preserving password reset flow that sends emails only to the original account address and revokes all active sessions upon reset. LoginSessionsController provides an admin-only interface to view and manage active login sessions. Additionally, the application introduces a new static badge endpoint (BadgeStaticController) for displaying generic badge values, a CriteriaController for browsing criteria details, and an UnsubscribeController for managing email notification preferences. The existing SessionsController is updated to handle OmniAuth failures gracefully and enforce login disable modes.

app/controllers · high confidence

New account activation confirmation page

A new view for account activation confirmation has been added, providing a user interface where users can confirm their email address. The page displays a localized heading and prompt, includes a hidden field for the user's email, and presents a primary button to submit the activation token via a PATCH request.

_app/views/account\activations · high confidence

New baseline criteria forms and project details UI

The project editing interface now supports the new baseline criteria series (baseline-1, baseline-2, baseline-3) alongside the existing passing, silver, and gold levels. New view templates (\_form\_baseline.html.erb, \_form\_baseline-1.html.erb, etc.) provide dedicated forms for these levels, including a version notice banner during transitions. A new \_details.html.erb partial adds expandable detail toggles to form fields, and \_form\_early.html.erb has been updated to display baseline-specific badges and navigation links.

app/views/projects · high confidence

New baseline criteria sync and AI-assisted machine translation workflows

This change introduces two new sets of Rake tasks to \lib/tasks\. The \baseline\ namespace (\baseline.rake\) provides commands to download, sync, validate, and generate migrations for the official OpenSSF Best Practices baseline criteria, keeping the application's criteria definitions up to date. Additionally, a comprehensive machine translation workflow is added via \machine\_translations.rake\ and \machine\_translation\_helpers.rb\, enabling users to export untranslated keys, import translations, and run automated AI-assisted translations (configurable via environment variables) for multiple locales, with support for tracking source changes and cleaning up obsolete machine translations.

lib/tasks · high confidence

New email templates for project lifecycle notifications

Added new email templates for notifying project owners about new project creation, badge level changes (gained, lost, or warned), project deletion, and monthly status announcements. These templates include unsubscribe links for reminders, display project statistics and achievement details, and support internationalization for better user communication.

_app/views/report\mailer · high confidence

New level conversion logic and symbol refinements for criteria handling

This change introduces two new model concerns to support updated criteria handling. The \LevelConversion\ module provides a \level\_to\_number\ method that maps criteria level names (including new 'baseline-1', 'baseline-2', and 'baseline-3' labels) to numeric values for consistent ordering and comparison across Project and Criteria models. Additionally, the \SymbolRefinements\ module adds Ruby refinements to the Symbol class, enabling convenient access to status and justification field symbols (e.g., converting a criterion name to \:description\_good\_status\).

app/models/concerns · high confidence

New models for additional project rights, login sessions, and password security

This change introduces several new model classes to support enhanced security and project management features. The \AdditionalRight\ model enables granting edit permissions to users who do not own a project, while \LoginSession\ and \PendingResubmission\ manage secure, HMAC-keyed login states and stashed form submissions to prevent data loss during logout. Security is further hardened by the \BadPassword\ model, which checks passwords against a known-bad list using HMAC-SHA512, and by encrypting user email addresses in the \User\ model using AES-256-GCM with blind indexes for search. Additionally, \ApplicationRecord\ provides CDN cache key helpers, \ProjectStat\ aggregates daily project and user statistics, and \NoDupCoder\ optimizes memory usage by freezing cached strings.

ruby · high confidence

New operational and analysis scripts for deployment, markdown processing, and security

This change introduces a suite of new scripts to the \script/\ directory to support various operational, analysis, and security tasks. Deployment workflows are improved with \script/deploy\, which gates production releases on GitHub check statuses, and \script/fastly\_test\ to verify CDN cache purging. Markdown handling is enhanced with \script/fix\_markdown.rb\ for linting, \script/compare\_markdown\_output.rb\ for output analysis, and \script/benchmark-restart-redcarpet.rb\ for performance testing. Security and compliance are supported by \script/get-sbom\ for Software Bill of Materials retrieval, \script/dependabot\_review\_due\ for dependency review tracking, and fuzzing targets \script/fuzz\_markdown\_processor.rb\ and \script/fuzz\_url\_validator.rb\. Additional utilities include \script/extract\_baseline.rb\ and \script/extract\_justifications.rb\ for data extraction, \script/find\_non\_english\_projects.rb\ for content analysis, and \script/gather\_postgres\_state\ for database diagnostics.

script · high confidence

New project statistics dashboard with charts and data export

Users can now view project statistics through a new dashboard featuring interactive line charts for metrics such as total projects, activity over the last 30 days, reminders, and badge achievements. The interface supports internationalization and includes a dedicated view for individual daily stat records. Administrators gain access to additional insights, including email addresses for reminder targets, while all users can download the underlying data in CSV or JSON formats.

_app/views/project\stats · high confidence

Behavioural changes

Add internationalized email templates for user account events

The application now uses internationalization (i18n) for user-facing emails, including account activation, password reset, GitHub welcome, direct messages, and user update notifications. These new templates in app/views/user\_mailer replace hardcoded text with translation keys, allowing the content of these emails to be localized for different languages.

_app/views/user\mailer · high confidence

Added asset manifest configuration

A new manifest.js file has been added to the assets configuration directory to explicitly define how stylesheets, JavaScript, and images are linked within the application's asset pipeline.

app/assets/config · low confidence

Added delayed job for CDN project purges with retry logic

A new \PurgeCdnProjectJob\ has been introduced to handle CDN cache purging asynchronously, addressing race conditions in cache invalidation. The job accepts a \cdn\_badge\_key\ to target specific resources and includes automatic retry logic with polynomial backoff (up to 5 attempts) for transient failures, ensuring robustness against API outages. This change also establishes a base \ApplicationJob\ class that discards jobs on deserialization errors.

app/jobs · high confidence

Adopts CDLA-Permissive-2.0 for new managed data

New content managed by the service is now released under the Community Data License Agreement - Permissive, Version 2.0 (CDLA-Permissive-2.0), replacing the previous CC-BY-3.0 or CC-BY-3.0+ licenses. This change is implemented by adding the full text of the CDLA-Permissive-2.0 license to the repository and updating the LICENSES directory documentation to reflect the new licensing terms for recent submissions.

LICENSES · high confidence

CSS architecture reorganized into modular SCSS files

The application's stylesheet has been restructured from a single or monolithic file into a modular SCSS architecture. The main manifest is now \application.scss\, which explicitly imports components in a specific order: Bootstrap framework, extensions, shared mixins, base styles, layout components (header, footer), and controller-specific styles. New partial files have been created for \\_base\, \\_header\, \\_footer\, \\_forms\, \\_projects\, \\_static\_pages\, \\_users\, \\_sessions\, \\_utilities\, \\_variables\, and others, replacing the previous \static\_pages.scss\ and \application.css\ structure. This change improves maintainability by separating concerns and allows for better organization of global, layout, and page-specific styles.

app/assets/stylesheets · high confidence

Complete rewrite of CI/CD configuration with pinned dependencies and Heroku stack alignment

The CI/CD pipeline has been completely reconfigured to use pinned Docker image digests for security and reproducibility, eliminating uncertified orbs in favor of native implementations for Codecov and Brakeman checks. The test environment now runs on the Heroku 26-build stack image to match production, replacing the previous Ubuntu-based images, and utilizes a dedicated Selenium Chrome container for system tests. Deployment is separated into a lightweight Node-based job, and the Heroku CLI is installed via a new setup script.

.circleci · high confidence

Database schema evolution and criteria updates

This location contains the database migrations that define the application's data structure and scoring logic. The changes include adding new assessment criteria (such as TLS, hardening, and continuous integration), renaming fields to reflect updated terminology (e.g., 'changelog' to 'release\_notes', 'oss' to 'floss'), and introducing new tables for features like user activation, reminders, and project statistics. It also covers structural improvements like adding indexes for performance, enforcing 'not null' constraints for data integrity, and migrating email storage to case-insensitive 'citext'.

db/migrate · high confidence

Database schema updated to version 8.1 with new tables and expanded project metrics

The database schema has been regenerated for Rails 8.1, introducing several new tables including \login\_sessions\ for tracking active user logins with HMAC-digested session IDs, \pending\_resubmissions\ to securely stash form data across re-login flows, and \additional\_rights\ to manage user permissions per project. The \projects\ table now includes fields for tiered baseline percentages (\baseline\_tiered\_percentage\), specific achievement timestamps for gold and silver badges, and a Common Platform Enumeration (CPE) identifier for vulnerability tracking. Additionally, the \project\_stats\ table has been expanded to record detailed daily metrics for higher-level badge tiers (baseline-1 through baseline-3) and user activity, while the \bad\_passwords\ table supports password strength validation.

db · high confidence

Documentation of logo sources and processing steps

A new NOTES file has been added to the project logos directory, documenting the original sources and processing steps for several project logos including Gnu, GnuTLS, Kubernetes, TUF, and AppArmor. This file records where the original images were downloaded from and the commands used to resize and optimize them for use on the front page.

app/assets/images/project-logos-originals · high confidence

Internationalized error messages and enhanced pagination controls

Form validation errors are now displayed using internationalized text via the new shared partial \\_error\_messages.html.erb\, ensuring consistent and localized messaging for users. Additionally, the pagination UI has been updated with a new \\_pagination.html.erb\ partial that integrates Pagy with Bootstrap styling and adds explicit 'First' and 'Last' navigation links to improve accessibility and ease of use when browsing through multiple pages.

app/views/shared · high confidence

Introduce frozen cache fragments and hardened session management

The application now uses a custom \cache\_frozen\ helper that stores view fragments as frozen \SafeBuffer\ objects, significantly reducing memory allocation and copying during high-traffic rendering. Session handling has been hardened with a new \LoginSession\ model, automatic timeouts after 48 hours of inactivity, and a 30-day absolute expiration limit. To prevent session fixation, the session is reset upon login while preserving only necessary keys like the forwarding URL. Additionally, login attempts are now rate-limited per user to prevent brute-force attacks, and unsubscribe tokens are generated using HMAC with time-based validation and key rotation support.

app/helpers · high confidence

Introduces new Badge, Criteria, Icon, and Translations models

The application now uses dedicated model classes to manage core data and rendering logic. The Badge model handles the creation, validation, and caching of badge instances (including both Metal and Baseline series) by loading SVG assets and extracting dimensions. The Criteria model manages the definition, localization, and filtering of security criteria across different levels, providing structured data for JavaScript consumption. The Icon model pre-renders Font Awesome 5 icon HTML for performance, and the Translations module centralizes the retrieval of translation keys for bulk export to the frontend.

app/models · high confidence

New criteria listing and detail views with autofill support

The application now provides dedicated views for listing all criteria and displaying individual criterion details, replacing the previous rendering logic. These new pages render criteria hierarchically and include support for displaying 'autofill' entries when available. The implementation also introduces view-level caching to freeze content ahead-of-time and fixes a previous issue where criterion markers were displayed unconditionally.

app/views/criteria · high confidence

New input validators for email, password, text, and URLs

The application now uses dedicated validators to enforce stricter input rules. Email addresses are validated against a standard format. Passwords are checked against a database of known bad passwords to prevent weak credentials. Text fields reject invalid control characters (except standard whitespace) to ensure data integrity and prevent database errors. URLs are validated to allow only safe schemes (http/https), valid domain names, and specific path characters, while rejecting dubious URLs like IP addresses or loopbacks and ensuring proper UTF-8 encoding.

app/validators · high confidence

New static pages for cookies, criteria, 404/409 errors, and robots.txt

The application now includes dedicated static views for cookies, criteria discussion, and criteria statistics, alongside optimized 404 and 409 error pages that are intentionally lightweight to mitigate abuse. A new robots.txt view dynamically restricts crawler access to user data and specific paths in production while blocking all crawling in development. The home page view has been updated to display project logos and social sharing links for Twitter, Reddit, Facebook, LinkedIn, Hacker News, and email.

_app/views/static\pages · high confidence

OpenSSF Baseline criteria version updated to v2026.08.28

The OpenSSF Baseline criteria version has been updated to v2026.08.28. This change updates the \CURRENT\_VERSION\ constant in \app/lib/baseline\_config.rb\, which controls the version displayed in badge text and determines which criteria are currently active for analysis. The \IN\_TRANSITION\ flag remains false, indicating this version is now the standard for all new and updated project analyses.

app/lib · high confidence

Rails 8.1 environment configuration overhaul

The application environment files (development, test, production, and the new fake\_production) have been updated to align with Rails 8.1 defaults and modern best practices. Key changes include replacing the deprecated \config.cache\_classes\ with \config.enable\_reloading\, configuring explicit memory cache stores with a custom \NoDupCoder\ to prevent duplication issues, and setting production logging to stdout with a default \:info\ level. Production now enforces SSL by default (overridable via \DISABLE\_FORCE\_SSL\), uses \Rack::Deflater\ for compression, and configures SMTP email delivery via environment variables. The test environment now raises errors on missing i18n keys and uses \Rack::Deflater\ to better mimic production behavior.

config/environments · high confidence

Rails 8.1 upgrade and baseline criteria synchronization configuration

The application has been upgraded to Rails 8.1, enabling framework defaults that include YJIT off in development, no JSON HTML-escaping, and relative-redirect raising. Configuration files have been added to support the OpenSSF Baseline criteria synchronization, including \baseline\_config.yml\ for source URLs and cache settings, and \baseline\_field\_mapping.json\ mapping baseline criteria to database fields. The \config/application.rb\ file now explicitly loads the \lib/\ directory for autoloading and configures \Rack::Attack\ middleware. Additionally, \config/puma.rb\ has been updated to use \solid\_queue\ as the ActiveJob backend and includes logic to purge CDN cache after booting.

config · high confidence

Redesign of user profile, edit, and index views with enhanced access controls

The user-facing views for listing, displaying, and editing profiles have been completely rewritten. The user index now supports admin-only multi-field search (by name and email) and displays the user's authentication provider. User profiles prominently display projects the user owns, has additional rights to, or can edit, and provide a direct link to the user's GitHub profile if applicable. The edit form allows users to update their name, email, preferred locale, and notification preferences, with password fields restricted to local accounts. Access to sensitive data, such as email addresses and the ability to delete accounts, is strictly gated behind admin or self-access checks, and email links are safely escaped. A new JSON API endpoint exposes user data, including project IDs and rights, with email and activation details visible only to the user or admins, supporting GDPR data portability.

app/views/users · high confidence

Redesigned login page with GitHub OAuth, local auth, and security hardening

The login interface has been replaced with a new view that prominently features a 'Log in with GitHub' button alongside a traditional email/password form. The GitHub login flow now correctly handles CSRF protection by emitting the necessary meta tag and uses same-origin referrer policies to prevent leaking return tokens to external providers. The local login form includes a 'remember me' checkbox, a link to password resets, and explicitly disables browser autocomplete for passwords to address security risks. Additionally, the page supports a configuration mode that can disable login entirely, and all text is internationalized.

app/views/sessions · high confidence

Redesigned site layout with internationalization and performance optimizations

The application's visual structure has been completely overhauled: the header now uses a standard Bootstrap navigation with a locale selector dropdown, and the footer displays OpenSSF and Linux Foundation logos alongside the Fastly CDN attribution. To support global users, the layout is fully internationalized (i18n), with locale-specific URLs and metadata for search engines. Performance is improved through deferred JavaScript loading, preloading of critical assets (stylesheets, fonts, images), and frozen caching of static layout elements. Additionally, a new 'system announcement' capability allows administrators to display site-wide alerts via environment variables, and CSRF meta tags are now conditionally rendered to preserve CDN caching for anonymous visitors.

app/views/layouts · high confidence

Restructured JavaScript asset pipeline and added automation highlighting

The JavaScript assets have been reorganized to improve load performance and maintainability. A new manifest file (application.js) explicitly requires jQuery 3, Bootstrap, and imagesloaded, while deferring Chart.bundle and chartkick to the project-stats page. A new automation-highlighting.js script automatically expands panels containing automated or overridden fields and scrolls to the first overridden field when a URL anchor is present. Additionally, criteria.js.erb now serves as a server-to-client bridge, injecting criteria definitions and translations into global variables for use by the project form.

app/assets/javascripts · high confidence

Rewrite of configuration initializers for criteria, routing, and security

The application's configuration in config/initializers has been significantly restructured. Criteria data is now loaded from YAML files at boot into centralized constants (FullCriteriaHash, CriteriaHash) and used to dynamically derive canonical section names, routing constraints, and CORS patterns, ensuring consistency between the backend and frontend. A new initializer manages section name redirects and badge level rankings. Security and performance have been hardened: CORS is now defined via regex patterns derived from the criteria data, a custom middleware fixes CDN cache-control issues, and cookie encryption rotations are configured for the transition to Rails 7.0 defaults. Additionally, the pagination library has been upgraded to Pagy 43 with a reduced default limit, and various other initializers for Fastly, i18n, and rate limiting have been updated or added.

config/initializers · high confidence

Updated OpenSSF Baseline badges to v2026.08.28

The static badge images in \app/assets/images\ have been updated to reflect the OpenSSF Baseline criteria version v2026.08.28. This includes new SVG assets for the baseline status levels (1, 2, 3) and the in-progress progress indicators (0%–20%), ensuring that the visual badges displayed on project pages accurately represent the current compliance standards.

app/assets/images · high confidence

Test coverage

Added OSS-Fuzz integration configuration for fuzz testing; Added Rails system tests for core application flows; Added controller integration tests for application, authentication, and badge services; Added integration tests for admin user visibility, CDN caching, session handling, and project workflows; Added mailer previews for user and report emails; Added model tests for core application components; Added tests for LevelConversion concern and SymbolRefinements; Added tests for PurgeCdnProjectJob; Added tests for config/initializers to ensure correct autoload ordering and coverage; Added tests for lib/ utilities; Added tests for login session revocation and machine translation helper tasks; Added tests for report and user mailers; Added unit tests for core analysis and security components; Added unit tests for helper methods; Test infrastructure overhaul: system tests, coverage, and VCR redaction; Updated test fixtures for OpenSSF badges and tiered feed data.

Dependencies

Upgrade to Rails 8.1 and pin Node.js 24 for builds

The application has been upgraded to Rails 8.1.1 (including all action\* gems and railties), replacing the previous 6.1.x release. To ensure consistent JavaScript minification during deployment, the Node.js version used by Heroku is now explicitly pinned to 24.19.0 via a new package.json file. Additionally, the Gemfile now loads only specific Rails components (such as actionmailer, actionpack, and activerecord) rather than the full rails gem to reduce memory usage and attack surface, and it introduces several new dependencies including solid\_queue for ActiveJob, sentry-rails for crash reporting, and a local fork of the redcarpet gem.

(dependencies) · high confidence

Housekeeping

Added placeholder files for asset and log directories

Empty .keep files were added to lib/assets, log, vendor/assets/javascripts, and vendor/assets/stylesheets to ensure these directories are tracked by version control.

lib/assets, log, vendor · 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 52 → 53 (+1.6)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 64 → 64 (+0.0)
  • Architecture 82 → 77 (-4.9)
  • Maturity 52 → 83 (+31.1)
  • Readiness 54 → 54 (+0.0)
  • Security 69 → 68 (-1.2)
  • Domain Modelling 48 → 48 (+0.0)
  • Accessibility 53 → 53 (+0.0)
  • Performance 90 → 90 (+0.0)

Resolved (4)

  • High: security finding (details withheld)
  • Outdated: commonmarker
  • Outdated: pagy
  • Outdated: webmock

New (3)

  • Outdated: scout_apm
  • Outdated: selenium-webdriver
  • Outdated: solid_queue

Changes since last survey

  • 22 commits — 22 feature/other, 0 fixes

By area

  • .circleci/config.yml — 7 commits
  • .github/workflows — 7 commits
  • (root) — 6 commits
  • .github/heroku-ruby-versions.txt — 1 commit
  • test/controllers — 1 commit

Notable commits

  • change: Bump renovatebot/github-action from 46.3.10 to 46.3.12 (#3110)
  • change: Bump renovatebot/github-action from 46.3.8 to 46.3.9 (#3084)
  • change: Bump renovatebot/github-action from 46.3.9 to 46.3.10 (#3096)
  • change: Bump step-security/harden-runner from 2.22.1 to 2.22.2 (#3083)
  • change: Bump step-security/harden-runner from 2.22.2 to 2.22.3 (#3097)
  • change: Bump the codeql-action group with 3 updates (#3091)
  • change: Bump the gems-minor group with 3 updates (#3093)
  • change: Bump the gems-minor group with 6 updates (#3109)
  • change: Bump the gems-patch group with 2 updates (#3092)
  • change: Bump the gems-patch group with 7 updates (#3108)
  • change: Improve update process (#3111)
  • change: Refresh the list of Rubies Heroku can deploy (#3095)
  • change: Update Rails to 8.1.4.1 and related gems (#3115)
  • change: Update cimg/node Docker tag to v26.12.1 (#3090)
  • change: Update cimg/node Docker tag to v26.13.0 (#3105)
  • change: Update cimg/postgres:18.6 Docker digest to b5646e1 (#3103)
  • change: Update cimg/postgres:18.6 Docker digest to d4c42df (#3088)
  • change: Update dependency ruby to v3.4.11 (#3058)
  • change: Update gem crass 1.0.7->1.0.8 (#3087)
  • change: Update heroku/heroku:26-build Docker digest to 1a234cc (#3089)
  • …and 2 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

ossf/best-practices-badge 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 100a704da6f6aea7572da16d6f45171f29acb7f5 — 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.2+preprod-5c4e66d9318b.