Skip to content
CAI
Software that uses CAICheck a score

ElMassimo/vite_ruby

54.8

Adequate · 6 November 2026

3.8k

lines of production code

Ruby

with TypeScript, JavaScript

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is a monorepo providing a suite of Ruby gems and JavaScript plugins that integrate the Vite frontend build tool with Ruby web frameworks, primarily Rails, Hanami, and Padrino. It manages the core runtime logic for asset compilation, development server proxying, and manifest handling, while offering framework-specific adapters and tag helpers for rendering assets in views. The project also includes example applications and legacy compatibility layers to support older Rails versions and browser requirements.

How it got here

2021 — ViteRuby core and monorepo restructuring

44 changes.

The project underwent a major architectural overhaul, splitting the monolithic codebase into a pnpm monorepo with a new ViteRuby core gem and specialized integration gems for Rails, Hanami, and Padrino. This period focused on modernizing the infrastructure by upgrading to Ruby 4.0 and Vite 8, removing legacy Vue scaffolding and standalone gems, and introducing comprehensive support for Server-Side Rendering and build caching.

2022–2023 — vite-plugin-rails launch and tooling rewrite

6 changes.

This period focused on launching vite-plugin-rails as an opinionated, pre-configured package for Rails applications, complete with a runnable example and comprehensive test coverage. Concurrently, the project's internal release and changelog tooling was rewritten in CommonJS to support automated versioning and commit validation for both JavaScript and Ruby components.

Features

Add Vite Rails Legacy entrypoint template for Rails 4

A new example entrypoint file (application.js) is provided for the Vite Rails Legacy integration, targeting Rails 4 applications. The template includes instructions for using the Vite client and JavaScript tags, notes on TypeScript and JSX/TSX support, and commented-out examples for integrating Hotwired Turbo, Active Storage, and glob-based channel imports.

_vite\_rails\legacy/templates/entrypoints · high confidence

Added ApplicationRecord base class for Rails examples

The Rails example application now includes an ApplicationRecord base class that inherits from ActiveRecord::Base and is marked as an abstract class, providing a standard foundation for application models.

ruby · high confidence

Added Procfile.dev template for local development server

A new Procfile.dev template has been added to the project, configuring the web process to start the Rails server via bin/rails server. This file supports local development workflows by providing a standard Procfile entry for running the application.

_vite\rails/templates · high confidence

Added base model class for the Administrator engine

The Administrator engine now includes an ApplicationRecord base class that inherits from ActiveRecord::Base. This provides a standard foundation for models within the engine, allowing them to inherit common database configuration and behaviors.

administrator · high confidence

Added development and release helper scripts

The vite\_ruby package now includes two executable scripts in the bin directory: a console script that launches a Pry REPL with the library loaded for interactive development, and a release script that delegates to pnpm to handle the release process for the vite\_ruby gem.

_vite\ruby/bin · high confidence

Added release script for vite\_plugin\_legacy

A new executable shell script named 'release' has been added to the vite\_plugin\_legacy/bin directory. This script serves as a wrapper that changes the working directory to the parent folder and invokes the 'pnpm release' command for the vite\_plugin\_legacy package, passing through any additional arguments provided by the user.

_vite\_plugin\legacy/bin · high confidence

Added release scripts for Hanami and Rails integrations

New executable release scripts have been added to the vite\_hanami and vite\_rails directories. These scripts allow users to trigger the release process for their respective integration packages directly from the command line by invoking the underlying pnpm release workflow.

_vite\_hanami/bin, vite\rails/bin · high confidence

Executable CLI entry point for ViteRuby

A new executable script at \vite\_ruby/exe/vite\ has been added to provide a command-line interface for the ViteRuby gem. This entry point initializes the environment, loads the core library, and invokes the \ViteRuby::CLI\ to allow users to run Vite-related commands directly from the terminal.

_vite\ruby/exe · high confidence

Hanami Bookshelf example app scaffolding and Vite integration

The Hanami Bookshelf example application has been scaffolded with a complete project structure, including environment configuration files for development and testing, Rakefile tasks for Vite, and a Vite configuration that utilizes the Ruby plugin. The app is configured to run on Ruby 3.1.1 and includes initial RSpec and Capybara test setups for controllers and views, providing a baseline for building Hanami applications with Vite.

_examples/hanami\bookshelf · high confidence

Initial example application for vite-plugin-rails

The \vite-plugin-rails/example\ directory now contains a complete, runnable example application demonstrating the new \vite-plugin-rails\ package. This example showcases a Vue 3 setup with Server-Side Rendering (SSR) support via Inertia.js, including specific configurations for development and production environments in \vite.json\ and \vite.config.ts\. It provides a reference implementation for users, featuring entrypoints for TypeScript, SCSS, and CSS, as well as an SSR server entry point.

vite-plugin-rails/example · high confidence

Initial template files for the vite\_ruby gem

This change introduces the default configuration and entrypoint templates for the newly separated vite\_ruby gem. It adds a Vite configuration file (vite.config.ts) that registers the Ruby plugin, a vite.json configuration defining source directories and specific development/test ports (3036/3037), and a basic application.js entrypoint. These files provide the foundational setup for integrating Vite with Ruby applications.

_vite\ruby/templates · high confidence

Integrates Vite.js for frontend asset management in the Padrino blog tutorial

The Padrino blog tutorial now uses Vite.js to handle frontend assets, replacing the previous setup. This integration adds a Vite configuration, a Ruby plugin for Vite, and specific HAML helpers (such as \vite\_client\_tag\ and \vite\_javascript\_tag\) to the application layout, allowing the app to serve modern JavaScript and CSS bundles. The example also includes a development Procfile to run the Vite dev server alongside the web server, enabling features like Hot Module Replacement (HMR) during development.

_examples/padrino\_blog\tutorial · high confidence

Introduce Vite Rails Legacy for Rails 4 compatibility

Adds the Vite Rails Legacy gem (v3.1.0), providing a compatibility layer for Rails 4 applications to use Vite. This includes a Rails Engine that registers tag helpers (such as \vite\_javascript\_tag\, \vite\_asset\_url\, and \vite\_image\_tag\) and configures the Vite Ruby proxy and logger. The configuration specifically handles legacy asset host setups by disabling support for Proc-based asset hosts, and the installation template automatically injects the necessary Vite tags into the default application layout.

_vite\_rails\_legacy/lib/tasks, vite\_rails\_legacy/lib/vite\_rails\legacy · high confidence

Introduce ViteHanami gem for Hanami integration

This change introduces the ViteHanami gem (version 3.0.0), which integrates Vite Ruby with the Hanami web framework. It provides tag helpers (such as \vite\_client\, \vite\_javascript\, and \vite\_stylesheet\) to render Vite-processed assets in Hanami views, and includes an installation script that automatically configures the Hanami app by injecting necessary middleware, updating the Content Security Policy for Hot Module Replacement, and adding Vite rake tasks to the Rakefile.

_vite\hanami/lib · high confidence

Introduce VitePadrino integration for Padrino applications

Adds the VitePadrino gem (v3.0.0) to enable Vite.js integration within Padrino apps. This includes tag helpers for rendering Vite-processed assets (scripts, stylesheets, and client tags for HMR), an installation script to configure the app and inject necessary tags into layouts, and a Rack middleware setup to proxy the Vite dev server in non-production environments.

_vite\padrino/lib · high confidence

Introduce VitePluginLegacy gem for legacy browser support

This change introduces the \vite\_plugin\_legacy\ gem (version 3.0.2), which provides Rails tag helpers to support legacy browsers via \@vitejs/plugin-legacy\. The gem automatically registers \VitePluginLegacy::TagHelpers\ in Rails controllers and views, exposing \vite\_legacy\_javascript\_tag\, \vite\_legacy\_typescript\_tag\, and \vite\_legacy\_polyfill\_tag\. These helpers render \\<script\>\ tags with the \nomodule\ attribute for polyfills and legacy entry points, ensuring compatibility with older browsers that do not support ES modules.

_vite\_plugin\legacy/lib · high confidence

Introduce vite-plugin-rails as an opinionated Vite plugin for Rails

A new \vite-plugin-rails\ package is added, providing a pre-configured Vite plugin tailored for Rails applications. It bundles \vite-plugin-ruby\, \vite-plugin-environment\, \vite-plugin-full-reload\, \vite-plugin-stimulus-hmr\, \vite-plugin-manifest-sri\, and \rollup-plugin-gzip\ (for gzip and brotli compression) into a single plugin with sensible defaults for Rails file structures. The plugin is ESM-only, targets Node 20, and includes a duplicate plugin detector to prevent configuration errors when migrating from \vite-plugin-ruby\.

vite-plugin-rails · high confidence

vite-plugin-ruby source code restructured and initialized

The \vite-plugin-ruby\ plugin source has been reorganized into a new \src/\ directory, introducing dedicated modules for configuration (\config.ts\), constants (\constants.ts\), and type definitions (\types.ts\). A new \dev-server.ts\ module handles dev server metadata and cleanup, while \manifest.ts\ manages asset fingerprinting. The plugin now supports SSR builds, additional entrypoints, and improved Windows path handling via a new \slash\ utility. A \dev-server-index.html\ is included to provide a helpful landing page when users visit the Vite dev server directly.

vite-plugin-ruby/src · high confidence

Removals

Removal of Vite plugin source code and workspace configuration

The source files for the Vite plugin (including configuration loading, context management, and type definitions) and the pnpm workspace configuration have been deleted from the package. This removes the plugin's ability to automatically detect entrypoints, load JSON configuration, and manage component contexts within the Ruby application environment.

package · high confidence

Removal of legacy Vite Rake task definitions

The \lib/tasks/vite/\ directory has been completely removed, eliminating the Rake tasks that previously handled Vite integration within Rails applications. This includes the deletion of tasks for building assets (\vite:build\), cleaning output (\vite:clean\), clobbering builds (\vite:clobber\), installing dependencies (\vite:install\_dependencies\), verifying installation (\vite:verify\_install\), providing environment info (\vite:info\), and generating binstubs (\vite:binstubs\). Applications relying on these specific Rake tasks for asset compilation or maintenance will need to adopt the new Vite integration methods provided by the updated gem structure.

lib/tasks · high confidence

Removal of the standalone vite\_rails gem

The \lib/vite\_rails\ directory and its associated Ruby classes (including \ViteRails\, \Builder\, \Config\, \Manifest\, and helpers) have been deleted. This change removes the standalone \vite\_rails\ gem, which previously handled Vite integration within Rails applications, indicating a shift to a different architecture or gem structure for Vite support.

_lib/vite\rails · high confidence

Behavioural changes

34 commits (12 fixes) modifying vite\_ruby/lib/vite\_ruby/cli

A change to existing behaviour in vite\_ruby/lib/vite\_ruby/cli — 34 commits (12 fixs), 10 files.

_vite\_ruby/lib/vite\ruby/cli · medium confidence · unverified

Added release script for vite\_padrino

A new executable release script has been added to the vite\_padrino/bin directory. This script facilitates the release process by changing to the project root directory and invoking the pnpm release command specifically for the vite\_padrino package, passing through any additional arguments.

_vite\padrino/bin · high confidence

Enforce commit message validation and staged linting via Husky

The project now automatically validates commit messages and lints staged files before every commit. A new commit-msg hook runs a verification script to ensure commit messages follow the required format, while a pre-commit hook executes lint-staged to check code quality on changes before they are committed.

.husky · high confidence

Example app restructured with Vue 3, TypeScript, and legacy browser support

The example application has been reorganized to demonstrate modern Vite and Vue 3 usage. The frontend assets have moved to a new \app/frontend\ directory structure, utilizing TypeScript for entrypoints (\main.ts\) and components (\HelloWorld.vue\, \App.vue\). The configuration (\vite.config.ts\) now uses \defineConfig\, includes an alias for \@assets\, and integrates \@vitejs/plugin-legacy\ to support older browsers like IE 11. Additionally, the example now includes a Server-Side Rendering (SSR) setup using Inertia.js and Vue 3, along with TypeScript declaration shims for \.vue\ and \.md\ files.

vite-plugin-ruby/example · high confidence

Hanami Bookshelf demo app migrated to Vite and Hanami 2

The Hanami Bookshelf example application has been updated to use the Hanami 2 framework and Vite for frontend asset management. This change replaces the previous Rails-based setup with a new Hanami application structure, including updated routing, controllers, and views. The frontend build process now leverages Vite, with assets compiled via \vite\_ruby\ and \vite\_hanami\ helpers, and the UI branding has been updated to reflect the Hanami framework.

_examples/hanami\bookshelf/apps/web · high confidence

Introduce ViteRuby singleton and core runtime API

The library now exposes a central \ViteRuby\ class that manages the application's configuration, command execution, and asset manifest. Users can access the singleton instance via \ViteRuby.instance\ to retrieve configuration, run Vite commands, or check if the development server is active. The class also provides a \digest\ method to generate a hash of watched files for asset versioning and supports environment variable overrides via \ViteRuby.env\. This change establishes the core runtime interface for the gem, replacing previous ad-hoc access patterns with a unified, instance-based API.

_vite\ruby/lib · high confidence

Project infrastructure overhaul and Ruby 4.0 support

The project has upgraded its runtime to Ruby 4.0.6 and switched its JavaScript package manager from Yarn to pnpm, introducing a pnpm workspace structure for the monorepo. Development tooling has been standardized with the adoption of the 'standard' Ruby linter, a new ESLint configuration, and a dedicated .node-version file for Node 24.20.0. Additionally, the repository now includes a Code of Conduct, a new logo, and updated documentation and contributing guides to reflect these structural changes.

(repo-wide) · high confidence

Rails example app modernized with Vite, React, Tailwind CSS 4, and Docker support

The Rails example application has been completely rebuilt to demonstrate modern Vite integration. It now uses React with the Vite React plugin, Tailwind CSS 4, and Hotwire Turbo. The setup includes Docker support via a new Dockerfile and docker-compose.yml, a Content Security Policy initializer, and error tracking integrations for Bugsnag and Honeybadger. Additionally, a new Rails engine example is included to showcase how to configure Vite within an isolated engine context.

examples/rails · high confidence

Rake tasks now integrate with Rails asset pipeline and support SSR builds

The \vite.rake\ file now defines specific tasks for building assets (\vite:build\, \vite:build\_ssr\, \vite:build\_all\) and installing dependencies, while automatically enhancing or defining the standard Rails \assets:precompile\ and \assets:clobber\ tasks. This ensures that Vite dependencies are installed and assets are bundled during the Rails precompile step, with support for Server-Side Rendering (SSR) builds when enabled. The integration also handles legacy npm and yarn version compatibility by setting appropriate environment variables during the precompile process.

_vite\ruby/lib/tasks · high confidence

Release tooling scripts rewritten in CommonJS

The repository's internal release tooling has been updated with new CommonJS scripts for generating changelogs, managing releases, and verifying commit messages. The new changelog script (scripts/changelog.cjs) automatically infers versions from Ruby gem version files for non-JS packages and generates changelogs using conventional-changelog. The release script (scripts/release.cjs) now supports both JavaScript and Ruby library releases, with specific handling for Ruby packages including Rubocop execution and version file updates. The commit verification script (scripts/verifyCommit.cjs) enforces conventional commit message formatting to ensure automated changelog generation works correctly.

scripts · high confidence

Removal of Vue-specific default installation template

The default installation files for the library have been removed, specifically the \lib/install\ directory which previously provided a Vue-based application scaffold (including \application.js\ with Vue imports, channel loading, and a red background CSS). This change eliminates the automatic setup of a Vue-specific frontend structure during installation, requiring users to provide their own entry points or choose a different framework configuration.

lib/install · high confidence

Standardized bin binstubs and added build/test helpers

The bin scripts for rake and rubocop have been updated to use double quotes for string literals, aligning with the project's standard style configuration. Additionally, new binstubs were introduced: 'bin/m' serves as a generic entry point for the 'm' gem, and 'bin/snapshot' automates the build and snapshot testing process for the vite-plugin-ruby package by installing dependencies, building the project, and copying the production output to the test app directory.

bin · high confidence

Updated example entrypoint to use @hotwired/turbo and modern glob imports

The example application entrypoint template has been updated to reflect current best practices for Rails integration. It now recommends using @hotwired/turbo instead of the legacy Turbolinks library, including the necessary start() call. Additionally, the example for loading Rails channels has been corrected to use the standard import.meta.glob with the eager option, replacing the outdated import.meta.globEager syntax. The template also includes helpful comments for TypeScript and JSX usage, along with a link to the official guide.

_vite\rails/templates/entrypoints · high confidence

Updated test matrix to support Rails 7.2, 8.0, and 8.1 while dropping EOL versions

The gemfiles used for testing have been updated to include new configurations for Rails 7.2, 8.0, and 8.1, allowing the library to be validated against these newer versions. Conversely, support for older, end-of-life Rails versions (5.2 and 6.0) has been removed from the test matrix. The 'rails-edge' configuration has also been refactored to use gemspec paths for the split gems (vite\_ruby, vite\_rails, vite\_plugin\_legacy) instead of the previous monolithic structure.

gemfiles · high confidence

Vite Rails integration now delegates to Vite Ruby and adds modern tag helpers

The \vite\_rails\ gem has been refactored to act as a thin adapter for the \vite\_ruby\ core, shifting the underlying build and configuration logic to that library. This change introduces a comprehensive set of new view helpers (\vite\_client\_tag\, \vite\_javascript\_tag\, \vite\_typescript\_tag\, \vite\_stylesheet\_tag\, \vite\_image\_tag\, and \vite\_picture\_tag\) that simplify rendering Vite assets in Rails views, including support for the \\<picture\>\ element in Rails 7.1+. The integration also automatically configures Content Security Policy (CSP) rules during installation to support Hot Module Replacement (HMR) and sets the \javascript\_path\ to ensure Zeitwerk ignores frontend source files.

_vite\_rails/lib/vite\rails · high confidence

vite-plugin-ruby v5.2.5 release with SSR, Vite 8, and configuration updates

The vite-plugin-ruby package has been updated to version 5.2.5, introducing several key changes for users. The plugin now supports Server-Side Rendering (SSR) builds via new configuration options like \ssrBuildEnabled\, \ssrEntrypoint\, and \ssrOutputDir\, allowing developers to enable experimental SSR capabilities. It also adds compatibility with Vite 8 (including Rolldown/Oxc), requiring users to ensure their Vite version is up to date. Additionally, the default source code directory has changed from \app/javascript\ to \app/frontend\, and new configuration options such as \additionalEntrypoints\, \packageManager\, and \skipProxy\ are available for more granular control over the build process. The plugin now uses \npx vite\ by default for execution and includes experimental support for the Bun package manager.

vite-plugin-ruby · high confidence

vite\_ruby 3.11.1: Upgrade to Vite 8 and introduce build caching

This release upgrades the default Vite version to 8 (Rolldown + Oxc) and updates the default plugin version to 5.2.5. It introduces a new build caching system that records build status, timestamps, and file digests to skip unnecessary rebuilds when watched files have not changed, improving build performance. The library also adds a CLI upgrade command, supports Ruby configuration files for advanced settings, and includes various fixes for package manager detection (including Bun), manifest handling, and error reporting.

_vite\_ruby/lib/vite\ruby · high confidence

Fixes

Fixes Rake task initialization and environment loading order

The Vite Rake tasks now correctly load the Rails environment before executing, preventing symbol errors and ensuring the application is fully initialized. This change also simplifies the installation of build dependencies by leveraging package manager flags and ensures that the Vite installation verification task is properly enhanced with the Rails environment dependency.

_vite\rails/lib/tasks · high confidence

Test coverage

Added Vite configuration and test app scaffolding; Added feature test for the admin home page; Added frontend entrypoint assets for the test application; Added test coverage for configuration, dev-server metadata, and entrypoints; Added test layout templates for dummy and test apps; Added test suite for vite-plugin-rails configuration and build output; Migrate test suite to ViteRuby and add comprehensive coverage; Removed test application JavaScript entrypoints; Updated test application configuration and added test fixtures; Updated test dummy app for Ruby 2.4 compatibility and SSR support.

Dependencies

Upgrade documentation site to Vite 8 and pnpm 12

The documentation site (docs/) has been updated to use pnpm 12.4.2 as the package manager and upgraded to Vite 8.2.1. The VitePress theme has been updated to version 2.0.0, and Vue has been bumped to 3.5.41. These changes ensure the documentation build environment stays compatible with the latest tooling versions.

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

Lenses

  • Code Health 60 → 60 (+0.0)
  • Architecture 81 → 81 (+0.0)
  • Maturity 43 → 65 (+21.2)
  • Readiness 50 → 50 (+0.0)
  • Security 60 → 62 (+2.2)
  • Domain Modelling 100 → 100 (+0.0)
  • Accessibility 51 → 51 (+0.0)
  • Performance 91 → 91 (+0.0)

Resolved (11)

  • Documentation: no installation or build instructions (docs/src/index.md)
  • Documentation: no project overview (docs/src/index.md)
  • Documentation: no usage examples (docs/src/index.md)
  • High CVE: [GHSA redacted] (pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
  • Inconsistent CLI/Installation entry points. ViteRuby (core) uses a CLI.Install.call method, while ViteRails (framework integration) uses an Installation class with separate setup methods. This creates confusion about where the installation logic lives and how to invoke it programmatically.
  • Inconsistent availability of URL vs Path helpers. ViteRails and ViteRailsLegacy expose both vite_asset_path and vite_asset_url, whereas ViteHanami and VitePadrino only expose vite_asset_path. This forces consumers to check which framework is in use to determine if a URL helper exists.
  • Inconsistent image helper signatures. ViteRails and ViteRailsLegacy have vite_image_tag but ViteRails also has vite_picture_tag. ViteHanami and VitePadrino lack image helpers entirely. Furthermore, vite_image_tag takes (name, options) while vite_picture_tag takes (sources, block), which is a distinct operation but highlights a lack of unified image handling strategy across the ecosystem.
  • Inconsistent installation API structure. ViteRails uses a CLI.Install class with separate methods for setup and CSP, while ViteHanami, VitePadrino, and ViteRailsLegacy use an Installation class with only setup_app_files and install_sample_files. The CSP setup is missing from the non-Rails frameworks.
  • Inconsistent naming convention for tag helpers. ViteHanami uses vite_javascript while VitePadrino, ViteRails, and ViteRailsLegacy use vite_javascript_tag. Similarly, ViteHanami uses vite_client vs vite_client_tag in others, and vite_react_refresh vs vite_react_refresh_tag.
  • Medium CVE: [GHSA redacted] (pnpm-lock.yaml)

New (47)

  • Critical CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
  • Critical CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • Critical CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • Critical CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [CVE redacted] (pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
  • …and 27 more

Architecture

  • Unchanged — 0 containers · 3 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

ElMassimo/vite_ruby 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 653767bda7f9ccae9556abe73b9bde2741dd9ef8 — 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.