rails/propshaft
57.6
Adequate · 6 November 2026
1.2k
lines of production code
Ruby
primary language
4
measurements over time
What this system is
Features
Added benchmark suite for asset resolution and compilation
A new benchmarking suite has been added to the \benchmarks\ directory to measure the performance of Propshaft's asset handling. This includes executable scripts for the CSS asset URL compiler, static resolver, and dynamic resolver, along with a \Trackrod\ helper class that generates synthetic test assets (images, CSS, and JavaScript) to drive these benchmarks. This allows users to quantify the impact of changes on compilation and resolution speeds.
benchmarks · high confidence
New release and test scripts added to bin
Added a new \bin/release\ script that automates the gem release process by updating the version file, committing changes, pushing tags, and publishing to RubyGems. Also added a \bin/test\ executable to simplify running the test suite using Bundler and Rails plugin test helpers.
bin · high confidence
Propshaft 1.3.2: Subresource Integrity, bulk stylesheet helpers, and asset server middleware
Propshaft has been upgraded to version 1.3.2, introducing Subresource Integrity (SRI) support for enhanced security. The \stylesheet\_link\_tag\ and \javascript\_include\_tag\ helpers now accept an \integrity: true\ option to automatically generate and include integrity hashes in secure contexts (HTTPS or local development). Additionally, these helpers support \:all\ and \:app\ symbols to include all known stylesheets or only those from the application's \app/assets\ directory, respectively. The asset server is now a proper middleware (\Propshaft::Server\) that can be enabled in development and test environments, and the \Propshaft::Helper\ module is automatically included in Action View. The manifest now supports integrity hashes and distinguishes between app and engine assets, while the load path prioritizes application assets over engine assets.
lib/propshaft · high confidence
Support for asset URL resolution in CSS, JavaScript, and source maps
Propshaft now includes dedicated compilers for resolving asset URLs within CSS (\url()\), JavaScript (\RAILS\_ASSET\_URL()\), and source map references (\sourceMappingURL\). These new components ensure that relative asset paths are correctly resolved, digested, and prefixed with the configured URL root, while also tracking dependencies between assets to ensure correct digesting when files rely on one another.
lib/propshaft/compiler · high confidence
Behavioural changes
43 commits (2 fixes) modifying propshaft
A change to existing behaviour in propshaft — 43 commits (2 fixs), 4 files: “Adds the clean \[count\] parameter that sprockets, webpacker and capistrano used (\#165)”; “Rely on real Pathname objects everywhere”; “Raise missing asset error in more places (\#16)”; and 39 more (refs \#165, \#16, \#7, \#17, \#100, …).
propshaft · medium confidence · unverified
New Rake tasks for asset management and debugging
The asset management rake tasks have been extracted into a dedicated file, introducing new capabilities for developers. A new \assets:clean\ task now accepts an optional \count\ parameter to control how many previous asset versions are retained, aligning with behavior from other asset pipelines. Additionally, a new \assets:reveal\ task (and its subtask \assets:reveal:full\) allows users to inspect the logical paths and full file paths of available assets. The \assets:precompile\ task now includes a warning when executed in the development environment to alert users that changed assets will not be served until the manifest is cleared.
lib/propshaft/railties · high confidence
Propshaft initializes its own logger and loads core components directly
Propshaft now manages its own logging infrastructure by storing a singleton logger instance (defaulting to STDOUT) and explicitly requiring its core components (Assembly, Errors, Helper) and ActiveSupport's delegation module at load time. This removes the previous reliance on ActiveSupport's autoload mechanism and the Railtie for basic initialization, ensuring the library is self-contained and ready to use even outside of a full Rails boot sequence.
lib · high confidence
Static resolver now reads from manifest and supports integrity checks
The static asset resolver has been refactored to initialize eagerly with a manifest object, enabling it to look up asset paths, integrity values, and app-specific assets directly from the manifest data rather than relying solely on disk lookups. This change introduces an \integrity\ method for Subresource Integrity support and adds configurable encoding options to the \read\ method, while also providing a warning mechanism when the manifest is outdated and cannot provide app asset paths.
lib/propshaft/resolver · high confidence
Test coverage
Added comprehensive test suite for Propshaft core components; Added dummy Rails application for integration testing; Added integration tests for asset resolution and integrity; Added test coverage for static and dynamic asset resolvers; Added test fixtures for CSS asset compilation; Added test fixtures for CSS dependency chains; Added test fixtures for asset path resolution and digested file handling; Added test fixtures for new manifest format with app key support; Added test fixtures for source map URL parsing edge cases; Added tests for CSS asset URL, JS asset URL, and source mapping URL compilers; Updated test fixtures for output manifest and assets.
Dependencies
Add dedicated Gemfiles for Rails 7.0–8.1 testing
The project now includes specific Gemfile variants for Rails versions 7.0, 7.1, 7.2, 8.0, and 8.1 to facilitate testing across these supported releases. For Rails 7.0 and 7.1, the setup pins minitest to versions below 6, while Rails 7.2, 8.0, and 8.1 utilize the minitest-mock gem. Each variant also includes standard dependencies like rake and debug, ensuring the library can be validated against the full range of supported Rails environments.
gemfiles · high confidence
Upgrade to Rails 8.1 and refine runtime dependencies
Propshaft now targets Rails 8.1.3, replacing the previous dependency on the full 'rails' gem with specific dependencies on 'actionpack' (\>= 7.0.0), 'activesupport' (\>= 7.0.0), and 'rack'. This change aligns the gem with the latest Rails release and reduces unnecessary runtime overhead by depending only on the frameworks actually used. Additionally, the project enforces Multi-Factor Authentication (MFA) for gem releases via metadata and adds Rubocop linting tools for development.
(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 58 → 58 (-0.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 75 → 75 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 54 → 54 (+0.0)
- Readiness 51 → 51 (+0.0)
- Security 79 → 76 (-3.6)
Resolved (2)
- Inconsistent naming for the primary lookup operation. LoadPath uses find, while its consumers (Resolver) use resolve. While these are different types, the semantic action 'look up an asset by logical path' is named differently across the API surface, suggesting a lack of a unified interface or consistent verb choice for asset retrieval.
- Redundant methods for adding entries to the manifest. push_asset likely wraps an asset into an entry and calls push, or performs the same logical operation. Having two distinct methods for the same intent (adding a manifest entry) creates confusion about which to use.
New (1)
- Medium CVE: [GHSA redacted] (Gemfile.lock)
Changes since last survey
- 3 commits — 2 feature/other, 1 fixes
By area
- .github/workflows — 2 commits
- lib/propshaft — 1 commit
Notable commits
- fix: fix CI workflow syntax issue (#288)
- change: Don't prioritize gems installed inside the application as app assets (#286)
- change: drop EOL ruby 3.1 and 3.2 from CI matrix (#287)
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
rails/propshaft 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 e7530a0490c8e1cd4e15dfa9a98717167fa6dccf — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-60d1b390edf0.