Skip to content
CAI
Software that uses CAICheck a score

rack/rack-attack

66.0

Adequate · 14 November 2026

820

lines of production code

Ruby

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Behavioural changes

11 commits (1 fix) modifying examples

A change to existing behaviour in examples — 11 commits (1 fix), 2 files: “Mitigate login throttle bypasses in docs”; “Add example instrumentation”; “feat: match ActiveSupport Instrumentation event name format spec”; and 7 more.

examples · medium confidence · unverified

137 commits (7 fixes) modifying lib/rack/attack

A change to existing behaviour in lib/rack/attack — 137 commits (7 fixs), 14 files: “refactor: DRY setting config defaults”; “Updated all non-secure HTTP URLs to HTTPS”; “Add 1 second buffer to expiry to correct throttles”; and 129 more (refs \#357, \#302, \#330, \#118, \#14, …).

lib/rack/attack · medium confidence · unverified

19 commits (1 fix) modifying gemfiles

A change to existing behaviour in gemfiles — 19 commits (1 fix), 18 files: “ci: test against ActiveSupport::RedisCacheStore v5 (\#632)”; “style: don't enforce rubocop in autogenerated files”; “Add Rails 8 to CI (\#677)”; and 15 more (refs \#632, \#677, \#671, \#721, \#631, …).

gemfiles · medium confidence · unverified

314 commits (19 fixes) modifying (repo-wide)

A change to existing behaviour in (repo-wide) — 314 commits (19 fixs), 9 files: “Consolidate \#testing section of README”; “Mitigate login throttle bypasses in docs”; “Updated all non-secure HTTP URLs to HTTPS”; and 278 more (refs \#632, \#357, \#671, \#658, \#706, …).

(repo-wide) · low confidence · unverified

51 commits (14 fixes) modifying lib/rack/attack/store\_proxy

A change to existing behaviour in lib/rack/attack/store\_proxy — 51 commits (14 fixs), 5 files: “Merge pull request \#482 from splitwise/rofreg/avoid-rails-5.2.4.3-deprecation-warning”; “refactor: avoid rescuing pattern repetition”; “Add a seperate cache-store proxy for the redis gem”; and 44 more (refs \#482, \#302, \#330, \#253, \#721, …).

_lib/rack/attack/store\proxy · medium confidence · unverified

98 commits (5 fixes) modifying lib/rack

A change to existing behaviour in lib/rack — 98 commits (5 fixs), 1 file: “refactor: prefer require over autoload for const referenced in the same file”; “Attempt to improve code legibility/clarity/semantics (\#357)”; “whitespace”; and 92 more (refs \#357, \#302, \#330, \#625, \#629, …).

lib/rack · medium confidence · unverified

Test coverage

12 commits adding/updating tests in spec/integration; 18 commits adding/updating tests in spec/acceptance/stores; 4 commits adding/updating tests in spec/support; 52 commits adding/updating tests in spec/acceptance; 98 commits adding/updating tests in spec.

Dependencies

76 commits updating dependencies (2 manifests)

A dependency / build maintenance change in (dependencies) — 76 commits (4 fixs), 2 files: “Gem release management. (\#614)”; “Updated all non-secure HTTP URLs to HTTPS”; “Use Appraisal to test against multiple versions”; and 67 more (refs \#614, \#706, \#302, \#330, \#715, …).

(dependencies) · medium confidence · unverified

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 66 → 66 (-0.5)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

Lenses

  • Code Health 76 → 74 (-1.9)
  • Architecture 69 → 69 (+0.0)
  • Maturity 58 → 58 (+0.0)
  • Readiness 79 → 79 (+0.0)
  • Security 94 → 89 (-4.2)

Findings

  • No change — the same findings as the prior survey.

Changes since last survey

  • 1 commits — 0 feature/other, 1 fixes

By area

  • (root) — 1 commit

Notable commits

  • fix: Fix Fail2Ban and Allow2Ban not banning with dalli 4 and 5 (#721)

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

Survey your own repository

rack/rack-attack 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 6e417ab3cacda0d3a604b625bb13dd0918816a82 — 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.