Skip to content
CAI
Software that uses CAICheck a score

softwaremill/retry

55.2

Adequate · 6 November 2026

413

lines of production code

Scala

primary language

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is a Scala library designed to provide resilience against transient failures by implementing configurable retry policies for asynchronous operations. It supports various delay strategies, including fixed pauses, exponential backoff with jitter, and immediate retries, while allowing users to define custom success conditions. The codebase has been consolidated into a single module, removing legacy dependencies on Netty and Twitter utilities in favor of a modern SBT 2.0 build structure.

Features

Initial release of retry library with multiple retry policies

This change introduces the 'retry' library (version 0.3.6), providing a set of retry strategies for Scala Futures. Users can now implement resilience against transient failures using policies such as Direct (immediate retry), Pause (fixed delay), Backoff (exponential delay), and FailFast (stop on specific exceptions). The library supports defining custom success conditions and integrates with various timer implementations for scheduling attempts.

(repo-wide) · high confidence

Introduce retry library with configurable backoff and jitter policies

The retry module now provides a comprehensive set of retry policies for handling transient failures. Users can choose between immediate retries, fixed delays, or exponential backoff strategies. The library includes a Jitter abstraction with four algorithms (none, full, equal, decorrelated) to randomize delays and prevent thundering herd problems, along with a Success type class to define which outcomes constitute success for retrying.

retry/src/main · high confidence

Removals

Removal of Netty-based timer implementation

The Netty-specific timer implementation (NettyTimer) has been removed from the codebase. This eliminates the dependency on the org.jboss.netty library for scheduling delayed operations, aligning with the shift to implement delay behavior in terms of odelay as indicated by the commit history.

netty · high confidence

Behavioural changes

Removal of Twitter-specific timer implementation

The custom \TwitterTimer\ adapter, which previously wrapped the Twitter Util \Timer\ to support retry delays, has been removed from the codebase. This change eliminates the dependency on the Twitter Util library for timer functionality, aligning with the shift to implement delay behavior using \odelay\.

twitter · high confidence

Removal of internal retry and timer implementation files

The internal implementation files for the retry mechanism (retries.scala, sleep.scala, and timer.scala) have been removed from the core module. This deletion eliminates the local definitions for retry strategies (Directly, Pause, Backoff), the Success predicate helper, and the underlying Timer and SleepFuture abstractions, indicating that this functionality has been refactored or replaced by external dependencies or other modules.

core · medium confidence

Test coverage

Added test coverage for retry policies and jitter algorithms

Added new test suites for the retry library, including JitterSpec to verify jitter algorithms (random, decorrelated, full, equal, none) and SuccessSpec to validate success predicates for Options, Eithers, and Trys. PolicySpec and its platform-specific variants (PolicySpecJVM, PolicySpecJS) were added to test retry policies such as Directly, Pause, and Backoff across JVM and Scala.js environments.

retry/src/test · high confidence

Dependencies

Migrate build to SBT 2.0 and SoftwareMill scaffolding

The project build has been restructured to use SBT 2.0.9 and the SoftwareMill sbt-softwaremill 3.0.1 plugin, replacing the previous multi-module layout (core, netty, twitter) with a single root project aggregating a unified 'retry' module. This change updates Scala versions to 2.12.19, 2.13.18, and 3.4.1, upgrades scalatest to 3.2.18, and adds dependencies on odelay-core and scala-collection-compat 2.12.0, while removing the legacy Netty and Twitter utility dependencies.

(dependencies) · high confidence

Migrated build system to sbt 2.0.9 with SoftwareMill plugins

The project's build infrastructure has been significantly updated by migrating from sbt 0.12.3 to version 2.0.9. The legacy \project/build.scala\ file, which defined a multi-module structure for \core\, \netty\, and \twitter\ subprojects, has been removed. It is replaced by a new \project/plugins.sbt\ configuration that integrates sbt-Scala.js 1.22.0, SoftwareMill common and publish plugins (version 3.0.1), and sbt-ide-settings 1.1.4.

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

Lenses

  • Code Health 76 → 76 (+0.0)
  • Architecture 69 → 69 (+0.0)
  • Maturity 43 → 43 (+0.0)
  • Readiness 66 → 64 (-2.4)
  • Security 77 → 61 (-15.5)
  • Performance 100 → 100 (+0.0)

Resolved (6)

  • Documentation: no architecture or design documentation (README.md)
  • Documentation: no project overview (README.md)
  • Off-boarding risk: anonymized user #1
  • Outdated: com.softwaremill.odelay:odelay-core_2.13
  • Outdated: io.github.cquiroz:scala-java-time_2.13
  • Outdated: org.scala-lang.modules:scala-collection-compat_2.13

New (2)

  • Dependency hygiene PARTLY measured — sbt declarations read, dependency currency not (Maven Central unreachable)
  • Off-boarding risk: anonymized user #1

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

Survey your own repository

softwaremill/retry 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 7ed571ddf58bb027444385936fa82cb286157fe2 — 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.