Skip to content
CAI
Software that uses CAICheck a score

basecamp/once-campfire

43.4

Weak · 14 November 2026

5.8k

lines of production code

Ruby

with JavaScript

8

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Added JSON view templates for bot messages

New Jbuilder templates have been added for the 'by\_bots' message scope, enabling JSON serialization for both the index and show actions. The index template renders a collection of messages using the shared 'messages/message' partial, while the show template renders a single message using the same partial, allowing API consumers to receive structured JSON responses for messages sent by bots.

_app/views/messages/by\bots · high confidence

Added backup and restore hooks for SQLite database management

New shell scripts have been added to the hooks directory to automate database backup and restore operations. The pre-backup hook executes a preparation script, while the post-restore hook automatically copies a SQLite snapshot from the storage backups directory to the active database location, ensuring the database is restored from the latest snapshot if one exists.

hooks · high confidence

Bot API for managing message boosts

A new controller endpoint has been added to allow bots to create and delete their own boosts (reactions) on messages. This feature enables bots to interact with message content by adding or removing boosts, with specific validation to ensure content is present during creation.

app/controllers/messages/boosts · high confidence

Introduces helper for push subscription session identification

A new helper method \push\_subscription\_session\_marker\ has been added to generate a session identifier for push subscriptions. This marker is derived from the current session's ID and creation time, allowing the browser to distinguish between different sessions without exposing sensitive token details.

app/helpers/users · high confidence

New benchmarking suite for HTTP throughput and message rendering performance

Added a new set of Ruby-based benchmarking tools in the \bench/\ directory to measure and compare application performance. The suite includes \compare\_http.rb\ for measuring HTTP throughput using production Puma/Redis configurations with isolated Docker containers, and \compare\_message\_hot\_paths.rb\ for analyzing rendering metrics such as query counts, allocations, and timing against frozen Rails sources. These tools utilize isolated seeds, specific CPU pinning, and strict response contracts to ensure accurate, reproducible comparisons between baseline and candidate code versions.

bench · high confidence

New script to generate secrets for self-hosting

A new executable script, script/admin/generate-secrets, has been added to help users set up self-hosted instances. When run, it generates and outputs the necessary environment variables: SECRET\_KEY\_BASE, VAPID\_PRIVATE\_KEY, and VAPID\_PUBLIC\_KEY, using Ruby's SecureRandom and the web\_push library.

script · high confidence

Redesigned setup script and added release automation

The local development setup experience has been significantly improved: the bin/setup script now uses a modern, interactive UI powered by 'gum' to guide users through installing system dependencies (like mise, sqlite, ffmpeg), Ruby gems, and Redis, while also installing GitHub Actions linting tools (actionlint, shellcheck, zizmor). Additionally, new bin scripts have been introduced to streamline operations: bin/release automates the creation of GitHub releases, builds multi-platform Docker images, and exports source code ZIPs for deployment; bin/ci integrates ActiveSupport's Continuous Integration; bin/bundler-audit and bin/thrust provide direct access to security auditing and the Thruster proxy; and bin/brakeman and bin/rubocop now run with explicit flags to ensure latest versions and use project-specific configurations.

bin · high confidence

Removals

Removed Trix rich text editor vendor file

The vendor JavaScript file for the Trix rich text editor (version 2.0.10) has been removed from the project.

vendor · high confidence

Security

Secured room message subscriptions and scoped unread streams

Room message subscriptions are now authorized at the time of subscription, ensuring that users can only access streams for rooms they currently belong to; revoking membership immediately stops message delivery. To support this, a new \RoomMessagesChannel\ handles the authorization logic, while the stock \Turbo::StreamsChannel\ is configured to reject requests for these specific streams, forcing all access through the new channel. Additionally, the unread rooms stream is now scoped per user (e.g., \user\_{id}\_unreads\) instead of being a global stream, preventing users from seeing activity in rooms they are not part of. The presence channel also now includes a timestamp with read broadcasts.

app/channels · high confidence

Security hardening and configuration updates in application initializers

This change introduces several security and stability improvements across the application's initialization phase. Active Storage direct upload endpoints are now protected by requiring a valid session, preventing unauthorized blob allocation or disk writes. Push notification deliveries are hardened against SSRF by pinning HTTP connections to the specific IP address resolved during subscription validation, and proxy discovery is disabled to prevent DNS rebinding. Image processing is secured by disabling untrusted libvips loaders (such as Openslide) and removing risky content types (BMP, ICO, Photoshop). Additionally, sensitive parameters like email, CVV, and CVC are now filtered from logs, and the HTTP acronym is registered for proper inflection. Other updates include configuring Redis via the REDIS\_URL environment variable, replacing the legacy SQLite3 initializer with dedicated WAL checkpointing and message count triggers, and updating time format registration to use the modern ActiveSupport API.

config/initializers · high confidence

Behavioural changes

Accurate room message counts via SQLite triggers

Room message counts are now maintained automatically by SQLite database triggers rather than application-level callbacks. This ensures that the \messages\_count\ on rooms stays correct even during bulk SQL operations, foreign connections, or migrations that bypass standard ActiveRecord callbacks, preventing stale or double-counted data. The system includes logic to install, repair, and backfill these triggers safely within write transactions.

app/models/room · high confidence

Admin-only room creation toggle and separated user list

The account settings page now includes a toggle switch that allows administrators to restrict new room creation to administrators only. Additionally, the account members list has been reorganized to display administrators separately from regular members, with a visual divider between the two groups.

app/views/accounts · high confidence

Adopt surfguard gem for private IP address validation

The private network guard in lib/restricted\_http now delegates IP resolution and blocking logic to the surfguard gem instead of using local IPAddr checks and the Resolv library. This ensures that internal, loopback, and link-local addresses are classified consistently across Basecamp, HEY, and Fizzy, while resolving issues with IPv6-to-IPv4 mapping and NAT64 ranges that were previously bypassed or incorrectly handled by the custom implementation.

_lib/restricted\http · high confidence

Asynchronous processing for room destruction and content moderation

The application now offloads specific resource-intensive operations to background jobs to improve responsiveness. Room destruction is handled by a new job that resets remote connections for former members and deletes messages one at a time within a single transaction. Additionally, a new job fans out unread room notices for messages, and a dedicated job handles the removal of banned content for users.

app/jobs · high confidence

Automated repair of room message counters and hardened SQLite WAL handling in background workers

The application now automatically repairs room message counts whenever the database schema is loaded or migrations run, ensuring data consistency without manual intervention. Additionally, background worker setup has been hardened to prevent SQLite Write-Ahead Log (WAL) checkpointing conflicts during process forking; the system now explicitly stops the WAL checkpointer before forking workers and restarts it afterward, while also switching Redis client reconnection to a close-and-reopen pattern to avoid inherited file locks.

lib/tasks · high confidence

The boosts section now renders preloaded boosts efficiently by sorting them by creation time when already loaded, or fetching them with the booster association when needed, eliminating redundant queries. The inline 'Add a boost' link is now wired to open the soft keyboard via a data attribute, and the boost partial's caching wrapper has been removed to ensure dynamic updates are reflected immediately.

app/views/messages/boosts · high confidence

Campfire runtime upgraded to Ruby 4.0.7 with performance and security enhancements

The application runtime has been upgraded from Ruby 3.3.1 to Ruby 4.0.7, requiring updated Docker base images and build dependencies (including libssl-dev). This release introduces native fragment caching with a bounded 64 MiB memory limit per worker to improve performance, and switches browser-side forgery protection to header-only checks (Sec-Fetch-Site) to simplify form handling while maintaining security. Additionally, the Docker image now runs as a non-root user, includes ONCE backup/restore hooks, and publishes OpenContainer annotations for better image metadata.

(repo-wide) · high confidence

Database schema updates for IP banning, user status, and room messaging

This release introduces several database schema changes to support new features and performance improvements. A new \bans\ table is added to store IP-based user bans, enabling administrators to block access by IP address. The \users\ table migrates from a boolean \active\ column to an integer \status\ column, with existing inactive users mapped to status 0. Account configuration is expanded by adding a \settings\ JSON column to the \accounts\ table, and a singleton guard constraint is added to ensure only one account exists. To improve messaging performance, composite indexes on \room\_id\ and \created\_at\/\updated\_at\ are added to the \messages\ table, and a \messages\_count\ column is added to the \rooms\ table with a backfill and trigger to maintain accurate counts. Additionally, standard Active Storage migrations are applied to support service names, variant records, and nullable checksums.

db/migrate · high confidence

Display file attachments in rich text by name without generating previews

When a file is attached directly to a message's rich text content, it is now rendered as a static link showing the file name and size instead of attempting to generate a visual preview. This change prevents unnecessary preview generation for file attachments that do not have one, ensuring a consistent and lightweight display for non-image files within message threads.

_app/views/active\storage · high confidence

The composer now saves and restores message drafts in local storage, preventing data loss when switching rooms. Link previews are handled by a new unfurl controller that fetches OpenGraph metadata via a dedicated API endpoint. The editor backend has migrated from Trix to Lexxy, requiring updates to autocomplete, reply formatting, and message reconciliation logic to ensure pending messages are correctly replaced by server broadcasts. Additionally, service worker registration now uses the full origin instead of just the host to fix localhost issues, and the rooms list preserves the direct message picker state during Turbo frame navigations.

app/javascript/controllers · high confidence

Enhanced security, caching, and session management in controller concerns

This update introduces several improvements to controller behavior: Active Storage direct uploads now require authentication to prevent unauthorized access; IP-based banning is enforced via a new concern that blocks requests from banned IPs with a 429 status; forgery protection is switched to header-only mode for better compatibility; session termination on logout now properly destroys the session record and disconnects remote connections; and response caching is refined to use record snapshots and fragment keys that include session tokens for improved cache isolation and performance.

app/controllers/concerns · high confidence

Enhanced security, performance, and access controls across the application

This update introduces several significant improvements to security, performance, and user access. Administrators can now restrict room creation to administrators only via account settings, and IP-based user banning is enforced through a new \BlockBannedRequests\ module. Performance is improved by caching read responses for messages, rooms, and searches, and by preloading only uncached messages to reduce rendering overhead. Additionally, bots are now allowed to update and destroy their own messages, and the unfurling of links is protected by a 10-second deadline to prevent slow external requests. Session management has been tightened by deleting server-side sessions on logout, and race conditions during first-run account creation are addressed with better error handling.

app/controllers · high confidence

Expanded bot message management and stricter access controls

Bots can now read, update, and delete their own messages, with the new \Messages::ByBotsController\ exposing index, create, update, and destroy endpoints that include pagination headers and room membership verification. Additionally, the ability for bots to remove their own boosts has been enabled by updating the \Messages::BoostsController\ to allow destruction of boosts where the bot is the booster, while ensuring boosts remain scoped to the current message.

app/controllers/messages · high confidence

Link previews are now restricted to external web URLs, preventing local host spoofing and ensuring previews only display content from other domains. The system also supports both legacy Trix and new Lexxy editor formats for these previews. Additionally, bot keys in request logs are now redacted to prevent accidental exposure of sensitive credentials.

_lib/rails\ext · high confidence

The link preview (Open Graph) fetching logic now enforces a 7-second timeout on all network operations (connection, read, and write) and disables automatic retries to prevent indefinite hangs. Additionally, the HTTP proxy is explicitly set to nil to prevent the \http\_proxy\ environment variable from bypassing the pinned IP address check, ensuring that requests always go to the verified destination. The response body is now buffered in a \StringIO\ object to correctly track byte size during chunked reading.

app/models/opengraph · high confidence

Hardened message content filtering with dedicated attribute sanitization

The content filtering system now includes a dedicated filter to scrub unsafe attributes (such as event handlers and dangerous URI schemes) from allowed HTML tags, ensuring that presentation styling classes are preserved while maintaining security. This change also refactors the handling of solo unfurled link text to support both Trix and Lexxy editors, and expands the set of allowed HTML tags to include additional formatting elements.

_app/helpers/content\filters · high confidence

IP-based user banning and push notification security hardening

Users can now be banned by IP address, preventing access from specific network locations while retaining their subscription data for potential unbanning. Banned users are excluded from receiving push notifications. Additionally, push subscription endpoints are now validated against a strict allowlist of permitted push service hosts and must resolve to public IP addresses to prevent Server-Side Request Forgery (SSRF) attacks.

ruby · high confidence

Improved HTML escaping for attribute safety

The \escapeHTML\ helper has been replaced with a new implementation that escapes quotes (\"\ and \'\) in addition to standard HTML entities. This change ensures that escaped strings are safe for use within HTML attributes, addressing potential security issues when rendering content like OpenGraph image URLs in link previews.

app/javascript/helpers · high confidence

Improved message attachment previews, search accuracy, and unread notification performance

Users will experience more reliable message posting and faster, more accurate search results. Attachment previews now handle large or unprocessable files gracefully by posting the message without a preview instead of failing, and video previews are generated as WebP posters. Search queries now correctly handle operator words (like 'AND' or 'OR') by quoting them, preventing parse errors, and search results are ordered by the index's rowid for better performance. Additionally, unread room notifications are now fanned out only to relevant users via a background job, reducing latency and ensuring notifications are sent only to those who haven't yet read the room.

app/models/message · high confidence

Improved reliability of video and image attachment previews

The attachment preview logic now handles cases where processing fails or is skipped due to file size limits. For videos, the poster image is only displayed if both the video preview and the poster variant have been successfully processed, preventing broken placeholders. For images, a thumbnail preview is shown only if it has been processed; otherwise, a simple link is rendered. This ensures users see valid content or a clear fallback rather than broken media elements.

app/helpers/messages · high confidence

Improved robustness and styling for Open Graph embeds

The Open Graph embed component now handles missing URLs more safely by only rendering the link when a href is present, preventing broken links. It also uses the description field instead of the caption for the embed text and applies a specific CSS class when a Twitter avatar is detected, ensuring better visual consistency and stability for users viewing rich link previews.

_app/views/action\text · high confidence

Introduces in-memory response caching and request-scoped session context

The application now caches HTTP responses in an in-memory store (backed by SQLite for version tracking) to reduce database load and collapse concurrent cold renders, while the \Current\ context model now tracks the active session to automatically resolve the associated user. This change improves performance for read-heavy operations by serving cached snapshots when available and ensures that session-based user identification is consistently available across the request lifecycle.

app/models · high confidence

Message presentation caching, RTL support, and editor migration

Message rendering now uses a versioned fragment cache key (presentation-v7) to ensure cache invalidation when presentation filters change, and the message list collection uses a specific cache key helper for consistent caching. The message body container now includes dir="auto" to automatically handle right-to-left language text direction. The rich-text editor in the message edit form has been migrated from Trix to Lexxy, updating the associated JavaScript controller actions and CSS classes. Additionally, the message actions partial is now wrapped in a cache block to optimize rendering, and the message creation Turbo Stream response now renders a pre-computed HTML fragment instead of the model object directly.

app/views/messages · high confidence

Migrate from Trix to Lexxy editor and update layout meta tags

The application replaces the Trix rich-text editor with Lexxy, evidenced by the new class name 'lexxy-content' in the Action Text layout and the introduction of custom 'lexxy-prompt-item' components for user autocompletion. Additionally, the application layout now includes a meta tag for script-aware Action Cable support and fixes HTML structure by removing unmatched closing spans from flash message icons.

app/views/layouts · high confidence

Migrate rich-text editor from Trix to Lexxy and update autocomplete requests

The rich-text editing engine has been replaced from Trix to Lexxy, introducing new support for citation nodes and updated allowed HTML elements while removing the previous Trix-based mention handlers and OpenGraph unfurling logic. Additionally, the autocomplete system now explicitly requests JSON responses by setting the Accept header, ensuring consistent data parsing for user suggestions.

app/javascript/lib · high confidence

Optimized message rendering with fragment caching

The search results view now renders messages using a partial with fragment caching enabled. This change reduces rendering overhead by caching individual message fragments, ensuring that only uncached or changed messages are re-rendered during page loads.

app/views/searches · high confidence

Rails 8 configuration updates and enhanced logging

The application environment configurations have been updated to align with Rails 8 and Ruby 3.4.5 standards. In development, code reloading is now managed via \config.enable\_reloading\ instead of the deprecated \config.cache\_classes\, and new logging features like query log tags, verbose enqueue logs, and view filename annotations are enabled. Production settings now use a custom \LogScrubbingFormatter\ to redact sensitive data from logs, implement granular cache-control headers for assets versus other files, and suppress deprecation reports. Test environment configurations have also been updated to use \enable\_reloading\ and raise errors for missing callback actions, ensuring stricter validation during testing.

config/environments · high confidence

Rails 8.2 upgrade, editor swap, and new bot/ban capabilities

The application has been upgraded to Rails 8.2 (config.load\_defaults 8.2), which includes switching the schema format from SQL to the default Ruby schema (schema.rb) and adjusting autoload settings. The rich text editor has been replaced from Trix to Lexxy, reflected in the importmap configuration. New functionality allows bots to read, create, update, and destroy their own messages and boosts via a new JSON API endpoint under /rooms/:room\_id/:bot\_key, and administrators can now ban users via a new /users/:user\_id/ban route. Configuration has also been hardened to support Redis connection via the REDIS\_URL environment variable, and database retry logic has been replaced with a timeout setting.

config · high confidence

Refactor PWA help view templates and update Edge install icon path

The PWA help and account settings views have been refactored to use the Herb compiler, which involves reformatting Ruby conditional logic within the ERB templates (specifically moving the \when\ clauses inside the \case\ blocks). Additionally, the instruction for installing the app on Edge now references the icon from the \external/\ directory (\external/install-edge.svg\) instead of the previous location.

app/views/pwa · high confidence

Refactor account logo serving and tighten user list visibility

The account logo controller now delegates image variant generation to a new account-level method, removing hardcoded resize constants and simplifying the controller logic. Additionally, the account members list now filters users to show only those visible to the current user, ensuring that non-visible or restricted accounts are not displayed in the member index.

app/controllers/accounts · high confidence

Refactor transfer form rendering structure

The view for the transfer show page has been updated to wrap the auto-submit form in a block syntax. This change modifies the internal structure of the view template without altering the visible user experience or the form's submission behavior.

app/views/sessions · high confidence

Refined room access control and scoping for specific room types

The room controllers now enforce stricter access rules and scope room lookups based on the specific room type being managed. The \ClosedsController\ and \OpensController\ restrict room creation to users with explicit permissions and scope room lookups to exclude direct rooms, preventing accidental conversion of direct rooms into open or closed types. The \DirectsController\ now sets the room instance variable for edit and destroy actions and scopes room lookups to only direct rooms, ensuring that users can only administer direct rooms they are part of. These changes enhance security by preventing unauthorized room type conversions and ensuring that users can only interact with the appropriate room types.

app/controllers/rooms · high confidence

Refined user management controls and banned state styling

The user list component now visually indicates when a user is banned by applying a 'banned' CSS class. Admin controls for role assignment are now disabled for the current user to prevent self-modification, and the delete button is explicitly hidden for the current user to prevent self-deletion. Additionally, the logic for displaying the 'My settings' link has been adjusted to ensure it appears for the current user regardless of admin privileges, while admin actions remain gated by active status.

app/views/accounts/users · high confidence

Replace Trix rich-text editor with Lexxy

The application's rich-text editing engine has been switched from Trix to Lexxy. This change updates the underlying editor components and their associated CSS, ensuring that the new Lexxy editor integrates seamlessly with the existing Campfire design system. Styles have been adjusted to map Lexxy's internal color palette to the app's light/dark themes, maintain consistent toolbar behavior, and preserve the look and feel of message bodies, embeds, and mention menus. A new cancel icon asset was added to support the updated UI elements.

app/assets, app/javascript, app/javascript/initializers · high confidence

Require current password for profile updates

The user profile page now includes a field to enter the current password before allowing changes to the profile. This adds a security step to ensure that the person making the update is the account owner, preventing unauthorized modifications even if the session is active.

app/views/users/profiles · high confidence

Restrict new room creation to administrators

The 'New Chat Room' button in the user sidebar is now conditionally hidden based on account settings. If the account setting 'restrict\_room\_creation\_to\_administrators' is enabled, only users with administrator privileges can see and click the button to create new rooms; regular users will no longer see this option.

app/views/users/sidebars · high confidence

Rich text editor replaced with Lexxy and Japanese language support added

The rich text editor has been replaced from Trix to Lexxy, requiring updates to the message sanitization logic to allow formatting tags (such as tables, strikethrough, and underlines) that were previously stripped. To ensure existing messages render correctly with the new editor, attachment content is now rebuilt from its source before editing. Additionally, Japanese translations have been added to the application's UI strings, and a helper was introduced to correctly configure ActionCable URLs when the application is served under a script name prefix. Also in this area: Require current password to change account password and resync push notifications; Improved URL and email linking in message text; Optimized response caching and authentication flow; Cached read responses and preserved request ports.

app/helpers · high confidence

SSRF protection and connection pooling for Web Push deliveries

Web Push notifications now include SSRF (Server-Side Request Forgery) protection by resolving the push service endpoint IP address before delivery, ensuring requests are pinned to a specific IP rather than allowing DNS rebinding attacks. Additionally, the library introduces a pooled connection system that reuses TLS connections to the same IP address, reducing handshake overhead and improving delivery performance while maintaining security through strict address pinning.

_lib/web\push · high confidence

Support Lexxy rich text editor mentions via new HTML response format

The users autocomplete controller now supports the Lexxy rich text editor's mention feature by rendering an HTML response without a layout for the \html\ format, specifically to return \\<lexxy-prompt-item\>\ elements. Additionally, the controller logic has been updated to accept a \filter\ parameter (in addition to the existing \query\ parameter) to accommodate Lexxy's filtering mechanism, ensuring that mentions are correctly filtered when the user types in the rich text editor.

app/controllers/autocompletable · high confidence

Switch database schema format from structure.sql to schema.rb

The database schema definition has changed from the database-specific \structure.sql\ to the database-agnostic \schema.rb\. This means that new environments are now set up by loading the Ruby schema file rather than executing raw SQL dumps, which improves portability across different database engines and simplifies version control of the schema definition.

db · high confidence

Switch rich-text editor from Trix to Lexxy and refine message formatting

The application replaces the Trix rich-text editor with Lexxy, updating the message formatting logic to handle Lexxy's specific output structure (using \lexxy-content\ classes and \\<br\>\ tags) and normalizing line breaks for syntax highlighting. Message class assignment is refactored to use a dedicated helper method for determining emoji-only messages, and the file uploader no longer manually sets the CSRF token header, relying on the browser's default behavior or other middleware.

app/javascript/models · high confidence

The room message composer has been replaced with Lexxy, introducing automatic draft saving when switching rooms and support for link unfurling. The composer now handles specific attachment types (mentions and opengraph-embeds) and utilizes a new 'unfurl' controller to process inserted links, enhancing the user experience when composing messages in real-time.

app/views/rooms · high confidence

User ban management and profile view updates

Administrators can now ban and unban users directly from the user profile page via a new ban button that triggers a confirmation dialog warning about logout, message deletion, and IP blocking. The profile view visually indicates when a user is banned, and the ban/unban action is conditionally shown only to administrators who are not viewing their own profile. Additionally, the user profile JSON serialization now includes an avatar URL, and inline mentions in text content are rendered as spans instead of divs to prevent paragraph breaking.

app/views/users · high confidence

User ban management, avatar caching, push subscription validation, and sidebar performance improvements

Administrators can now ban and unban users via the new BansController. Avatar serving has been optimized by moving the WebP variant configuration to the User model and leveraging etag-based caching to reduce rendering overhead. Push subscription endpoints now validate data before processing and return appropriate HTTP status codes (200 or 422) instead of always returning 200. The sidebar controller now caches its response and uses more efficient scope-based queries to load direct and shared room memberships, reducing database joins and rendering time. Also in this area: Improved session handling for password changes and invalid records; Require current password to change account password and resync push notifications.

app/controllers/users · high confidence

User banning, avatar variants, and bot authentication fixes

This update introduces IP-based user banning, allowing administrators to ban users by IP address, which automatically closes remote connections, deletes active sessions, and schedules the removal of banned content. User avatars now support a square WebP variant (512x512) for optimized display. A security fix ensures bot authentication correctly filters for active bots only, preventing potential impersonation via inactive bot tokens. Additionally, user mentions now use a custom content type for better attachment handling, and the user role enum is explicitly typed.

app/models/user · high confidence

Test coverage

Added integration tests for the bot messages API; Added system tests for composer, message integrity, and unread notifications; Added tests for Action Text attachables, OpenGraph embeds, and log scrubbing; Added tests for ActionCable channel authorization and unread room scoping; Added tests for ApplicationCable connection session lifecycle; Added tests for SQLite WAL checkpointing and libvips loader policy; Added tests for SSRF protections and metadata sanitization in link previews; Added tests for Web Push connection pooling, SSRF prevention, and badge counting; Added tests for bot message boost API; Added tests for caching, message presentation, and room lifecycle behaviors; Added tests for efficient direct room lookup; Added tests for message creation, search, and attachment handling; Added tests for message presentation, rich text editing, and content filtering; Added tests for private network guard SSRF protections; Added tests for push subscription validation and delivery; Added tests for room creation restrictions and type conversion safeguards; Added tests for room message counter integrity and push notification safety; Added tests for the UploadedScriptGuard middleware; Added tests for the auto-submit transfer form structure; Added tests for user avatar variants and bannable visibility; Expanded controller test coverage for caching, security, and messaging; New test helpers for DNS, push service, and rich text editor; Test infrastructure updates for rich text and parallel execution; Tests for Content Security Policy enforcement and asset restrictions; Tests for password-change security and push subscription race conditions.

Dependencies

Upgrade to Rails 8.2.0 alpha and update core dependencies

The application has been upgraded from Rails 7.2.0 alpha to Rails 8.2.0 alpha, requiring updates to core gems such as Puma (6.4 to 7.2), Redis (4.0 to 5.4), and Resque (2.6 to 2.7). The rich text editor has been switched from Trix to Lexxy, and the \surfguard\ gem has been added to handle SSRF address policies. Additionally, \bundler-audit\ was added to the development group for security auditing, and standard library gems like \ostruct\ and \benchmark\ are now explicitly declared.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 43 → 43 (+0.5)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

Lenses

  • Code Health 45 → 45 (-0.0)
  • Architecture 81 → 88 (+7.4)
  • Maturity 59 → 59 (-0.1)
  • Readiness 66 → 66 (+0.0)
  • Security 61 → 60 (-1.1)
  • Domain Modelling 47 → 47 (+0.0)
  • Accessibility 33 → 34 (+0.9)
  • Performance 100 → 100 (+0.0)

Resolved (5)

  • Duplicated block (9 lines × 2) (db/migrate/20231215043540_create_initial_schema.rb)
  • No ADRs found
  • Off-boarding risk: anonymized user #1
  • Outdated: sqlite3
  • Projects may be oversized for their cohesion

New (9)

  • Edited copies of one member (3 members, 4+ corresponding lines) (app/helpers/application_helper.rb)
  • No ADRs found (Procfile)
  • Off-boarding risk: anonymized user #1
  • Orphaned file (app/helpers/rooms_helper.rb)
  • Orphaned file (app/models/opengraph/metadata/fetching.rb)
  • Orphaned file (app/models/sound.rb)
  • Orphaned file (config/environments/test.rb)
  • Orphaned file (db/migrate/20231215043540_create_initial_schema.rb)
  • Orphaned files with no living knowledge

Changes since last survey

  • 9 commits — 9 feature/other, 0 fixes

By area

  • (root) — 4 commits
  • bin/release — 4 commits
  • (repo) — 1 commit

Notable commits

  • change: Build the release image from the committed tree
  • change: Check the release tag through gh, and stop when the check fails
  • change: Export the release ZIP from the committed tree
  • change: Merge pull request #437 from basecamp/puma-8-0-3
  • change: Tag the release at the commit being released
  • change: Update Rails to main at 8b06b0eb (#423)
  • change: Upgrade puma to 8.0.3
  • change: dep: update rails-html-sanitizer, loofah, and nokogiri (#421)
  • change: dep: update sqlite3 and crass (#418)

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

basecamp/once-campfire 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 14 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 7b809885a194f4c2f06f4f43e8e34704968f543e — the exact code this score is about.
  • Scored under rubric-2026.11.4 — 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.65+preprod-36d4cd83012f.