Skip to content
CAI
Software that uses CAICheck a score

bullet-train-co/bullet_train

45.1

Weak · 6 November 2026

3.6k

lines of production code

Ruby

with JavaScript

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add Avo admin panel controllers

This change introduces the Avo admin panel by adding new controller stubs for Invitations, Memberships, Teams, and Users. These controllers inherit from Avo's base resource controller to enable standard Rails resource routing for the new administrative interface.

app/controllers/avo · high confidence

Add Docker development and production entrypoint scripts

New shell scripts have been added to bin/docker-dev and bin/docker to manage the container lifecycle and execution environment. The bin/docker-dev scripts (build, console, create, destroy, shell, start, stop) provide a workflow for building and interacting with a development container named untitled\_application\_dev, including mounting the local app directory and setting the database username. The entrypoint scripts in both directories enable jemalloc for performance and automatically run db:prepare when starting the Rails server or dev process, ensuring the database is ready upon container launch.

bin/docker, bin/docker-dev · high confidence

Added Action Cable consumer and channel loader

The application now includes a dedicated entry point for WebSocket communication via Action Cable. A new consumer module initializes the connection using the @rails/actioncable package, and an index file is provided to automatically load all channel definitions following the \*\_channel.js naming convention, although the automatic loading mechanism is currently marked as incompatible with the esbuild bundler.

app/javascript/channels · high confidence

Added address hierarchy models

Introduced new model classes for the address domain, specifically \Addresses::Continent\, \Addresses::Country\, \Addresses::Region\, and \Addresses::Subcontinent\. These models inherit from \ApplicationHash\ and include respective base modules, establishing the foundational structure for geographic address data.

app/models/addresses · high confidence

Creation of shared views directory

A new shared views directory has been established at app/views/shared to house reusable view components. This structural change moves the placeholder file from the test fixtures location to the application's view hierarchy, ensuring the directory exists for future shared UI elements.

app/views/shared · high confidence

Initial API v1 JSON views and OpenAPI documentation

This change introduces the foundational view templates for the API v1 endpoints, enabling the serialization of Team, User, Membership, and Invitation resources into JSON. It also adds the OpenAPI v3.1 specification file which documents these resources, defines Bearer token authentication, and includes cursor-style pagination headers. Additionally, the User JSON view now conditionally exposes team\_id and team\_name fields when a user acts as a platform agent, supporting integrations like Zapier.

app/views/api · high confidence

Introduce Avo admin panel resources for core entities

This change adds the Avo admin panel resource definitions for Invitation, Membership, Team, and User models. These resources configure the fields displayed in the admin interface, including text fields for identifiers and names, select inputs for time zones (populated from ActiveSupport::TimeZone), and association fields (belongs\_to/has\_many) to manage relationships between users, teams, memberships, and invitations. This enables administrators to view and edit these core entities through the Avo dashboard.

app/avo · high confidence

Introduce account-scoped controllers with super scaffolding support

The application now includes a dedicated \Account::ApplicationController\ that serves as the base for all account-related controllers, introducing an \ensure\_onboarding\_is\_complete\ hook to manage user onboarding flows. New controllers for Dashboard, Invitations, Memberships, Teams, and Users have been added, each including a specific \ControllerBase\ concern. These controllers are structured to support 'super scaffolding', providing explicit \permitted\_fields\, \permitted\_arrays\, and \process\_params\ methods where developers can easily insert custom logic and permitted attributes for new model attributes.

app/controllers/account · high confidence

Introduction of core model infrastructure for permissions, data structures, and request context

This change introduces three new foundational models in the application. The \Ability\ class establishes the authorization framework by integrating CanCanCan with a custom \Roles::Permit\ module, enabling role-based access control that automatically parses permissions from \config/roles.yml\ and supports conditional logic for billing and Stripe integrations. The \ApplicationHash\ class provides a base for managing static data structures using the ActiveHash gem, facilitating associations for non-persistent data. Additionally, the \Current\ class is added as a wrapper around \ActiveSupport::CurrentAttributes\, including a base module to manage request-scoped state (such as the current user) throughout the application lifecycle.

app/models · high confidence

New Zapier integration for Creative Concepts and Tangible Things

This change introduces a new Zapier integration that allows users to connect their teams via OAuth2 and automate workflows. Specifically, it adds two triggers to detect when a 'Creative Concept' or a 'Tangible Thing' is created, and two corresponding actions to create new Creative Concepts and Tangible Things programmatically. The integration handles authentication, webhook subscriptions for real-time triggers, and API calls to the platform's scaffolding endpoints.

zapier · high confidence

New public home page with Tailwind CSS styling

A new public home page view has been added at app/views/public/home/index.html.erb, replacing previous implementations. The page features a centered layout using Tailwind CSS utility classes, displaying the Bullet Train logo and version number, a welcome message with a link to documentation, and a primary 'Sign In' button. It also includes a scroll-reveal animation effect for visual polish.

app/views/public · high confidence

New public-facing controller structure with modular features

The application introduces a new controller hierarchy for public pages, starting with a base \Public::ApplicationController\ that sets the 'public' layout. The \Public::HomeController\ now inherits from this base and integrates three specific capabilities via modules: \RootRedirect\ to handle root URL redirection (either to a marketing site or sign-in), \InviteOnlySupport\ to enforce invitation-only sign-ups, and \DocumentationSupport\ to expose developer documentation at \/docs\.

app/controllers/public · high confidence

Architecture

Refactored core models to use modular concerns and updated base class configuration

The core domain models (User, Team, Membership, Invitation, Address) have been restructured to include specific modular concerns (e.g., \Users::Base\, \Teams::Base\) instead of relying on inline Devise modules or empty shells. The \ApplicationRecord\ base class now includes \Records::Base\ and uses \primary\_abstract\_class\, centralizing default model functionality that can be opted out of by inheriting directly from \ActiveRecord::Base\. This change shifts the architecture from monolithic model definitions to a composition-based approach using extracted concerns.

ruby · high confidence

Behavioural changes

Added builds directory placeholder

A new 'builds' directory has been created in the assets folder, populated with a .keep file to ensure the directory is tracked by version control. This change appears to be a structural adjustment to the asset pipeline organization, likely preparing for future build artifacts or configuration.

app/assets/builds · low confidence

Added user account view partials for extensible fields and OAuth integration

The user account view now includes dedicated partials to support dynamic field rendering and OAuth provider integration. A new \\_fields.html.erb\ partial has been added to allow new user model fields to be inserted into the account interface, while \\_oauth.html.erb\ renders the Stripe accounts index for the current user when Stripe is enabled, providing a structured location for additional OAuth providers.

app/views/account/users · high confidence

Application identity and asset pipeline configuration updates

The application session key has been renamed from '\_shinkansen-app\_session' to '\_untitled\_application\_session' to reflect the application's new name. The asset pipeline has been updated to use Propshaft, with specific exclusions added for Avo, Cloudinary, Doorkeeper, and Bullet Train theme assets to prevent unnecessary files from being published during precompilation. Additionally, the API version is now explicitly set to 'v1' via the new api initializer.

config/initializers · high confidence

Configuration process split into modular, isolated scripts

The monolithic \bin/configure\ script has been refactored into a suite of smaller, independent Ruby scripts within the \bin/configure-scripts\ directory. This change allows individual setup steps—such as checking Ruby and Yarn versions, renaming Git remotes, setting up GitHub, updating application configuration, and adding deploy buttons for Heroku or Render—to be executed in isolation. Users benefit from a more transparent and flexible setup experience, where specific configuration tasks can be reviewed or re-run without re-executing the entire process.

bin/configure-scripts · high confidence

Created dedicated fonts asset directory

A new directory structure for font assets has been established at app/assets/fonts, populated by moving the placeholder .keep file from test/fixtures. This change organizes font resources separately from test fixtures, ensuring a clearer separation of concerns for application assets.

app/assets/fonts · low confidence

Custom Rake tasks for Action Text, Stimulus, AWS, ERD, and coverage reporting

This change introduces several new Rake tasks in the \lib/tasks\ directory to customize development and deployment workflows. The \action\_text:install\ and \stimulus:manifest:update\ tasks are overridden to skip execution by default, preventing redundant configuration and protecting custom manifest files, with the ability to force execution via the \--clobber\ flag. A new \aws:set\_cors\ task allows users to configure CORS permissions on their S3 bucket, while \auto\_generate\_diagram.rake\ ensures the \rails-erd\ tool correctly loads all Active Record models. Additionally, \coverage\_report.rake\ provides CI-friendly tasks to collate and format test coverage data, including specific grouping for Bullet Train core gems.

lib/tasks · high confidence

Database schema evolution and structural refactoring

This update applies a comprehensive series of database migrations that establish the foundational schema and progressively refactor it. Initial changes introduce core entities such as Users, Teams, Memberships, and API Keys, alongside features like two-factor authentication, webhooks, and role-based access control. Subsequent migrations refactor the data model by migrating from simple boolean flags to a granular Role system, consolidating OAuth integrations via Doorkeeper, and replacing legacy storage fields with Rails Active Storage and Action Text. The schema also expands to support team-level time zones, user locales, and collaborative editing on Creative Concepts, while removing deprecated tables and columns to clean up the database structure.

db/migrate · high confidence

Database schema upgraded to Rails 8.1 with expanded model support

The database schema has been regenerated for Rails 8.1.3, introducing support for new core features and integrations. Users will now have access to tables for address management, Stripe integration installations, and bulk onboarding invitation lists. The schema also includes standard Rails 8 components such as Action Mailbox, Action Text, and Active Storage, alongside updated OAuth tables for improved access token handling. Additionally, the database seeding process has been enhanced to automatically configure a platform application for Zapier if the Zapier app is detected in the environment.

db · high confidence

Default theme set to light and base helper included

The ApplicationHelper now includes the Helpers::Base module and defines a current\_theme method that returns :light. This ensures that the application defaults to the light theme and provides access to shared helper functionality.

app/helpers · high confidence

Environment-specific seed scripts with console output

The application now includes dedicated seed scripts for the development, production, and test environments. These scripts provide immediate console feedback upon execution and, in the test environment, include a specific stub to verify the \seeding?\ state of ActiveRecord models when triggered via the \seed\_stub\ environment variable.

db/seeds · high confidence

Extracted OAuth callback logic to shared integrations

The OAuth callback handling for the account area has been refactored to extract core logic into the \bullet\_train-integrations\ package. The local controller now inherits from the shared base and delegates specific provider handling (such as Stripe Connect) to the centralized callback method, allowing external packages to register OAuth providers automatically.

app/controllers/account/oauth · high confidence

Fixes Rails 7.2 constant loading error for OAuth scaffolding support

The \lib/bullet\_train\_oauth\_scaffolder\_support.rb\ file now explicitly defines the \BulletTrainOauthScaffolderSupport\ module to prevent a \NameError\ that occurs in Rails 7.2 when the file is required but contains no top-level constants. This change ensures that the OAuth provider integration target file loads correctly without throwing an uninitialized constant error, maintaining compatibility with the updated Rails version.

lib · high confidence

Mailer styles now use a dedicated PostCSS configuration

The mailer stylesheet pipeline now uses a dedicated PostCSS configuration file that dynamically loads Tailwind CSS settings via a Ruby script. This setup explicitly includes postcss-css-variables to support CSS variables in email clients, despite their limited support, and utilizes tailwindcss/nesting for nested CSS syntax.

_postcss\_mailer\config · high confidence

Migration to Webpacker and Bullet Train npm packages

The JavaScript build system has been updated to use Webpacker, replacing the previous asset pipeline configuration. The application now imports core functionality via the \@bullet-train/bullet-train\ npm package, including specific modules for sorting (\@bullet-train/bullet-train-sortable\) and Trix editor integration. Default Rails components like Active Storage and Turbo are explicitly imported, and legacy global jQuery definitions have been removed in favor of modern module imports.

app/javascript · high confidence

New API v1 controllers for core resources and authentication refactor

This change introduces new API v1 controllers for Invitations, Memberships, Teams, and Users, each inheriting from a shared base and including specific controller modules to handle request parameters. The previous Api::V1::AuthenticatedController, which handled HTTP basic authentication via API keys, has been removed. Instead, the Api::V1::ApplicationController now includes Api::Controllers::Base, centralizing authentication and base behavior for the new controllers.

app/controllers/api · high confidence

New account navigation menu structure

The shared account menu has been restructured to organize navigation into distinct sections: Teams, Integrations, Developers, and Team settings. The menu now conditionally renders items based on feature flags (such as billing, webhooks, and scaffolding) and user permissions. It also introduces a separate 'Your Account' section that is only displayed when the menu is in an expanded state.

app/views/account/shared · high confidence

Prepared Membership views for dynamic field scaffolding

The Membership view templates (\_attributes.html.erb and \_fields.html.erb) now include specific comment markers that allow the super scaffolding system to dynamically insert new fields. This change enables future updates to add new attributes to the Membership model without requiring manual edits to these view partials, as the scaffolding tool will automatically place new inputs above the designated insertion points.

app/views/account/memberships · high confidence

Rails 8.0 upgrade and application rebranding

The application has been upgraded to Rails 8.0, updating configuration defaults and enabling bootsnap for faster boot times. The application module and database names have been changed from 'ShinkansenApp' to 'UntitledApplication', and the database adapter now supports concurrent test runs via git worktree suffixes. Additionally, the Puma server configuration has been updated to use a dynamic thread pool, preload apps, and support Solid Queue, while the CI configuration now includes an Importmap vulnerability audit step.

config · high confidence

The public error pages (400, 404, 406, 422, 500) have been completely redesigned with a modern, responsive layout that supports dark mode, replacing the previous static dialog style. A new 406 Unsupported Browser page has been added to handle browser compatibility issues. Additionally, the robots.txt file has been updated to point to the current official documentation URL.

public · high confidence

Refactor ApplicationMailer to use Base module

The ApplicationMailer class has been refactored to include the Mailers::Base module, replacing the previous default configuration for the 'from' address and mailer layout. This change centralizes common mailer behavior and configuration within the Base module, potentially affecting how default sender addresses and layouts are applied to outgoing emails.

app/mailers · medium confidence

Refactor authentication and authorization into concerns and channels

The \AuthenticatedController\ class has been removed, consolidating authentication logic into the \Controllers::Base\ concern included in \ApplicationController\. Authorization is now handled via a \current\_ability\ method in the ActionCable channel, and WebSocket connections now explicitly identify and validate the \current\_user\ via Warden. Additionally, CSRF protection in the application controller is configured to run first using \prepend: true\.

app/controllers · high confidence

Refactor layout structure and update meta tags for Turbo and mobile support

The application layout has been restructured to extract head content into a partial (\\_head.html.erb\), replacing the previous monolithic \application.html.erb\. This change updates the meta tags to include \turbo-cache-control\ for Turbo compatibility, adds \mobile-web-app-capable\ support for iOS, and conditionally loads the Cloudinary widget and intl-tel-input utilities. The legacy \mailer.html.erb\ and \mailer.text.erb\ layouts have been removed.

app/views/layouts · high confidence

Refactored Devise authentication views and added modular OAuth component

The authentication UI has been restructured to support modular, composable components. A new shared partial \\_oauth.html.erb\ was added to render OAuth provider buttons (such as Stripe) within a grid layout, allowing for easy integration of additional providers via scaffolding. Concurrently, several legacy Devise view files (\passwords/edit.html.erb\, \passwords/new.html.erb\, and \shared/\_links.html.erb\) were removed, indicating a shift away from the default Devise view structure toward this new componentized approach.

app/views/devise/shared · high confidence

Refactored setup process into modular, independent scripts

The monolithic \bin/setup\ script has been replaced by a suite of independent, executable scripts in \bin/setup-scripts/\ (e.g., \brew\_bundle.rb\, \check\_postgres.rb\, \yarn\_install.rb\). This modularization allows the setup process to check for and install specific dependencies—such as Homebrew packages, PostgreSQL, Redis, Node.js, Yarn, and image processing tools—separately. The new structure also introduces more granular control, allowing users to skip optional checks (like \icu4c\ if \bullet\_train-conversations\ is absent) and enabling non-breaking behavior when services like Redis or PostgreSQL are not immediately available.

bin/setup-scripts · high confidence

Refined account menu with conditional team and admin options

The shared account menu now includes a dedicated 'Edit account details' item and conditionally displays 'Switch teams' for users in multiple teams or 'Add new team' for those who can create one. Additionally, users with developer privileges will see a new 'Admin' link pointing to the Avo admin panel, while the logout option remains available for all users.

app/views/account/shared/menu · high confidence

Removal of Sprockets asset manifest

The Sprockets asset manifest file (manifest.js) has been deleted, indicating that the application is no longer using the Sprockets asset pipeline for managing JavaScript and CSS assets. This change aligns with the migration to Propshaft, which handles asset serving differently and does not require this explicit manifest configuration.

app/assets/config · high confidence

Removal of custom Devise email templates

The application no longer uses custom HTML templates for Devise authentication emails. Specifically, the views for confirmation instructions, password change notifications, reset password instructions, and account unlock instructions have been deleted. Users will now receive the default Devise email formats for these actions instead of the previously customized versions.

app/views/devise/mailer · high confidence

Removal of custom Devise login view

The custom login page template for Devise sessions has been removed from the application. Users will now see the default Devise login interface instead of the previous custom form that included email, password, and remember-me fields.

app/views/devise/sessions · high confidence

Removal of legacy Sprockets JavaScript manifest and Action Cable setup

The application has removed the legacy Sprockets JavaScript manifest (application.js) and the Action Cable client configuration (cable.js). This indicates a migration away from the traditional Rails asset pipeline and bundled WebSocket support, likely towards a modern JavaScript bundler or a different real-time communication strategy. Additionally, the ApplicationJob base class now includes commented-out examples for automatic retry on deadlocks and discarding on deserialization errors, serving as documentation for available job resilience patterns without enabling them by default.

app/assets/javascripts, app/jobs · high confidence

Removed custom Devise confirmation and unlock views

The application no longer uses custom views for the 'Resend confirmation instructions' and 'Resend unlock instructions' flows. The specific ERB templates for these Devise actions have been deleted, meaning users will now see the default Devise UI for these operations instead of the previously customized forms.

app/views/devise/confirmations, app/views/devise/unlocks · high confidence

Removed default Devise registration views

The default ERB templates for the user sign-up and account-edit pages have been deleted from the application. This removes the built-in UI for registration and profile updates, indicating that these views are no longer served directly by this location and likely replaced by componentized or alternative implementations elsewhere in the codebase.

app/views/devise/registrations · high confidence

Repository restructured with new configuration files and deployment templates

The repository has been restructured to support modern development and deployment workflows. This includes adding a production Dockerfile and a development-specific dev.Dockerfile, along with a .dockerignore file to optimize build contexts. Deployment configurations for Heroku (app.json) and Render (render.yaml) have been introduced to streamline one-click deployments. The project now specifies Ruby 4.0.3 and Node.js 24.15.0 via .ruby-version and .nvmrc files, and introduces a Brewfile for Homebrew dependency management. Additionally, new configuration files such as .standard.yml for code linting, .yarnrc.yml for Yarn settings, and .redocly.yaml for API documentation are included to standardize the development environment.

(repo-wide) · high confidence

Reworked bin scripts with modular setup and new automation tools

The bin directory has been significantly restructured to improve modularity and developer experience. The monolithic \bin/setup\ and \bin/configure\ scripts have been split into smaller, independent sub-scripts (e.g., \bin/setup-scripts/\, \bin/configure-scripts/\) that handle specific tasks like dependency checks, database preparation, and GitHub integration. New automation tools have been added: \bin/bump-core\ for updating core gem and npm package versions (with GitHub Actions integration), \bin/secrets\ for generating environment-specific encrypted credentials, \bin/db\_schema\_check\ to prevent uncommitted schema changes, and \bin/set-ngrok-url\ to automatically update the base URL during local development. Additionally, \bin/dev\ now defaults to using \overmind\ if available, \bin/super-scaffold\ is deprecated in favor of the Rails generator, and legacy scripts like \bin/spring\, \bin/bundle\, and \bin/update\ have been removed to reduce overhead.

bin · high confidence

Stimulus application initialization with global debugging and controller merging

The JavaScript controllers entry point now initializes a Stimulus application that automatically loads local controllers while merging definitions from the @bullet-train/bullet-train, @bullet-train/fields, and @bullet-train/bullet-train-sortable packages. It registers global 'reveal' and 'scroll-reveal' controllers, initializes CableReady for real-time updates, and exposes the Stimulus application instance on the window object to enable browser console debugging of controller actions and lifecycle hooks.

app/javascript/controllers · high confidence

Switches application CSS to use Bullet Train theme system

The application stylesheet now imports the theme's default styles via the $ThemeStylesheet postcss resolver instead of using the previous require\_tree directive. This change integrates the Bullet Train theme system, allowing users to customize styles by ejecting the theme's CSS locally or adding custom CSS in the designated section, which helps avoid merge conflicts during framework updates.

app/assets/stylesheets · high confidence

Team show page now renders Creative Concepts via scaffolding

The team show page has been updated to display Creative Concepts associated with the team. This is achieved by rendering a new partial for Creative Concepts, which is conditionally included only if scaffolding features are not disabled. A placeholder comment has also been added to the team fields partial to support future field additions via the scaffolding system.

app/views/account/teams · high confidence

Updated Rails environment configurations to align with modern Rails defaults and Bullet Train conventions

The development, production, and test environment configurations have been updated to reflect newer Rails conventions and Bullet Train-specific requirements. In development, code reloading is now controlled via \config.enable\_reloading\ instead of the deprecated \config.cache\_classes\, and new logging features like server timing, verbose query logs, and view annotation are enabled by default. Production settings now use \enable\_reloading = false\, serve static files conditionally based on the \RENDER\ environment variable, and support Postmark or Mailgun for email delivery. Test environment configurations now enable eager loading in CI, use \:rescuable\ exception handling, and integrate Capybara Lockstep middleware for improved system test stability. Additionally, webhook header namespaces and Active Storage service defaults (local, Amazon S3, or Cloudinary) are standardized across all environments.

config/environments · high confidence

Test coverage

Added FactoryBot factory definitions for scaffolding test data; Added OpenAPI validation and API test base class; Added controller tests for the TangibleThings API resource; Added example factories for test data generation; Added integration tests for account controllers; Added mailer preview classes for Devise, User, and Webhook emails; Added model tests for user details, invitations, abilities, and Stripe webhooks; Added system test coverage for core application features; Added system test for device\_test migration script; Added system tests for super scaffolding scenarios; Added system tests for the Audit Logs gem; Added test coverage for API v1 Teams and Users controllers; Added test coverage for platform access tokens and application provisioning; Added test factories for outgoing webhook models; Added test factories for platform access tokens and applications; Added test factory for OAuth Stripe accounts; Added test factory for Scaffolding::AbsolutelyAbstract::CreativeConcept; Added test factory for StripeInstallation; Added test infrastructure scripts for Action Models and Audit Logs system tests; Added test support utilities and fixtures; Added tests for Action Cable connection and Redis adapter compatibility; Added tests for SuperSelectSupport concern; Added tests for application controller localization logic; Enhanced test infrastructure with coverage reporting and parallel execution support.

Dependencies

Initial JavaScript dependency setup for Bullet Train v1.45.1

The project now includes a \package.json\ and \yarn.lock\ file, establishing the JavaScript dependency tree for the application. This setup pins core Bullet Train packages (\@bullet-train/bullet-train\, \@bullet-train/fields\, \@bullet-train/bullet-train-sortable\) to version 1.45.1, alongside essential frontend libraries such as Stimulus, Turbo, Tailwind CSS, and esbuild. It also configures Yarn 4.2.2 as the package manager and defines build scripts for asset compilation, ensuring the frontend tooling is ready for development and production builds.

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

Lenses

  • Code Health 45 → 45 (+0.0)
  • Architecture 83 → 83 (+0.0)
  • Maturity 54 → 57 (+3.1)
  • Readiness 42 → 42 (-0.0)
  • Security 38 → 38 (+0.8)
  • Domain Modelling 100 → 100 (+0.0)
  • Accessibility 74 → 74 (+0.0)
  • Performance 100 → 100 (+0.0)

Resolved (8)

  • High CVE: [GHSA redacted] (yarn.lock)
  • High CVE: [GHSA redacted] (yarn.lock)
  • High CVE: [GHSA redacted] (yarn.lock)
  • High CVE: [GHSA redacted] (yarn.lock)
  • Medium CVE: [GHSA redacted] (yarn.lock)
  • Medium CVE: [GHSA redacted] (yarn.lock)
  • Medium CVE: [GHSA redacted] (yarn.lock)
  • Medium CVE: [GHSA redacted] (yarn.lock)

New (9)

  • High CVE: [GHSA redacted] (yarn.lock)
  • High CVE: [GHSA redacted] (zapier/yarn.lock)
  • High CVE: [GHSA redacted] (yarn.lock)
  • Medium CVE: [GHSA redacted] (zapier/yarn.lock)
  • Medium CVE: [GHSA redacted] (yarn.lock)
  • Medium CVE: [GHSA redacted] (zapier/yarn.lock)
  • Medium CVE: [GHSA redacted] (yarn.lock)
  • Medium CVE: [GHSA redacted] (yarn.lock)
  • Outdated: rails

Changes since last survey

  • 6 commits — 6 feature/other, 0 fixes

By area

  • (root) — 5 commits
  • config/environments — 1 commit

Notable commits

  • change: Add AWS_S3_* env vars with fallback to generic AWS_* vars (#2582)
  • change: Update all Yarn dependencies (2026-10-23) (#2580)
  • change: Update all Yarn dependencies (2026-10-28) (#2584)
  • change: Update all Yarn dependencies (2026-10-29) (#2588)
  • change: Update all Yarn dependencies (2026-11-05) (#2594)
  • change: Update crass to version 1.0.8 (#2587)

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

bullet-train-co/bullet_train 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 b895ccc12bb341016fc1d648414af6c38f13d816 — 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.