neosloc archive

Repositories /

Textualize/rich

https://github.com/Textualize/rich · commit 9d8f9a372cc5 · evaluated 2026-10-07 with neosloc 0.8.0 · JSON

2.00 integrability index over 7 applicable dimensions
library surfaces
$1.1M → $225k classic COCOMO → neosloc value (20% survives)
buy make / buy = 2203.14 over 3 years

Dimensions

Interface surface 4 exemplary An API reference is generated from the code (autodoc, mkdocstrings, typedoc, …).

Can another program use it through a documented, machine-readable surface?

library ladder · level 4

  • ✓ L1 An importable, packaged API exists. pyproject.toml Python package rich
  • ✓ L2 The public API is delimited (__all__, an exports map, exported identifiers). rich/__init__.py __all__
  • ✓ L3 The public API is statically typed (py.typed, type declarations, a typed language). rich/py.typed py.typed
  • ✓ L4 An API reference is generated from the code (autodoc, mkdocstrings, typedoc, …). docs/source/conf.py 2 matches
Contract stability 4 exemplary Across tagged releases, no OpenAPI operation, CLI option or __all__ symbol was removed without first being deprecated.

Can integrators rely on it not changing under them?

all ladder · level 4

  • ✓ L1 Releases are versioned (semver tags or versioned changelog sections). 177 semver tags, latest v15.0.0
  • ✓ L2 A changelog exists and marks breaking changes. CHANGELOG.md marks breaking changes
  • ✓ L3 A deprecation mechanism is used in code (warnings, @deprecated, Deprecation/Sunset headers) or the API is versioned. rich/live.py 1 matchrich/progress.py 1 match
  • ✓ L4 Across tagged releases, no OpenAPI operation, CLI option or __all__ symbol was removed without first being deprecated. 20 tagged releases compared
Events n/a Not applicable: no service and no long-running CLI mode (batch CLIs, libraries and desktop apps have no events).

Can others react to state changes without polling?

Identity n/a Not applicable: uses no credentials and has no service surface.

Can a machine act with its own revocable, least-privilege identity?

Data portability n/a Not applicable: owns no persistent data.

Can its data get in and out, in bulk, in open formats, with an explicit schema?

Agent ergonomics 2 partial Inputs are validated with messages naming the bad argument.

Can an automated caller use it without guessing, and recover from failure?

  • next: L3 Timeouts and retries are configurable. (no timeout parameter)

library ladder · level 2

  • ✓ L1 Errors are specific exception types, and library code never calls sys.exit. rich/errors.py 9 matchesrich/layout.py 2 matches
  • ✓ L2 Inputs are validated with messages naming the bad argument. rich/color.py 4 matchesrich/markup.py 4 matches
  • ✗ L3 Timeouts and retries are configurable. no timeout parameter
  • ✗ L4 Agent docs, and examples that run as tests (doctests). no agent docs
Embeddability 2 partial Installable as a package (a package manifest).

Can another system run and compose it without a human?

  • next: L3 Published to a public registry, with at most 10 runtime dependencies. (not published to a registry)

library ladder · level 2

  • ✓ L1 Importable from source. pyproject.toml Python package rich
  • ✓ L2 Installable as a package (a package manifest). pyproject.toml package manifest
  • ✗ L3 Published to a public registry, with at most 10 runtime dependencies. not published to a registry
  • ✗ L4 Optional features behind extras/features. no optional extras
Extensibility 0 absent Not yet: Internal seams: a registry, registration function or plugin manager.

Can behaviour be added without modifying the code?

  • next: L1 Internal seams: a registry, registration function or plugin manager. (no registry or registration function)

all ladder · level 0

  • ✗ L1 Internal seams: a registry, registration function or plugin manager. no registry or registration function
  • ✗ L2 The docs show how to add behaviour through those seams (even in-tree). no registration functions to document
  • ✗ L3 Out-of-tree extensions are discovered (entry points, a plugin directory, configuration) without editing the package. extensions must be added inside the package
  • ✗ L4 The extension API is versioned, has lifecycle hooks, and has example extensions. the extension API isn't versioned
Observability 0 absent Not yet: Logs through a standard logger namespace and never prints from library code.

Can an operator, or an orchestrating agent, tell whether it works and why not?

  • next: L1 Logs through a standard logger namespace and never prints from library code. (library code prints: rich/prompt.py, rich/abc.py, rich/scope.py)

library ladder · level 0

  • ✗ L1 Logs through a standard logger namespace and never prints from library code. library code prints: rich/prompt.py, rich/abc.py, rich/scope.py
  • ✓ L2 Log levels are used meaningfully (at least two levels). levels: critical, debug, error, exception, info, warning
  • ✗ L3 Optional metrics or tracing hooks. no metrics or tracing hooks
  • ✗ L4 OpenTelemetry instrumentation available. no OpenTelemetry instrumentation
Change legibility 2 partial CI runs the tests; applications pin dependencies (libraries and zero-dependency projects are exempt).

Can an agent change it safely with limited context?

  • next: L3 At least 90% of modules fit 32k tokens and no file exceeds 12k; test/source token ratio at least 0.3; at least 70% of the code is typed. (50% of modules fit 32k tokens; 3 files over 12k)

all ladder · level 2

  • ✓ L1 A README and some tests. README.mdtests/conftest.py 66 test files
  • ✓ L2 CI runs the tests; applications pin dependencies (libraries and zero-dependency projects are exempt). .github/workflows/codeql.yml.github/workflows/codespell.yml
  • ✗ L3 At least 90% of modules fit 32k tokens and no file exceeds 12k; test/source token ratio at least 0.3; at least 70% of the code is typed. 50% of modules fit 32k tokens; 3 files over 12k
  • ✗ L4 No import cycles, and agent docs (AGENTS.md, CLAUDE.md, llms.txt). 1 import cycles (largest: rich/__main__.py, rich/_log_render.py, rich/_palettes.py)

Make or buy

Make with agents

1,212,842 output + 30,321,050 input tokens on anthropic:claude-opus-5-5 ≈ $48.

13.5 agent-hours · 101.4 human days (10.5 steering + 90.9 rediscovering history).

$78,916 over 3 years

Buy (adopt as is)

15 min to running (via library) + 2 min to first use (via library).

5 min/year of upgrades; price $0/year.

$36 over 3 years

Buying wins below $26,293 per year. How this is estimated.

Classic COCOMO vs neosloc value

Classic COCOMO (sloccount)

34.84 KSLOC → 99.8 person-months over 14.4 months.

$1.1M

The effort to write it by hand, as COCOMO priced it in 1981.

neosloc value (neoCOCOMO)

Reproduce with agents: 16.7 PM (×0.17 of classic; 85% of behaviour captured by tests, contract and docs).

Rediscover uncaptured history: 4.3 PM (598 fixes in 3387 commits by 303 authors).

× leverage 1 (integrability) × obsolescence 0.95.

$225k (20.0 PM)

What survives

20% of the classic figure

21% of the replacement cost lives only in code and history.

How the value is estimated.

History

2026-10-07: 22026-10-07: 22026-10-07: 22026-10-07: 2
EvaluatedCommitneoslocIndexMake or buy
2026-10-079d8f9a372cc50.8.02.00buy
2026-10-079d8f9a372cc50.7.42.00buy
2026-10-079d8f9a372cc50.7.32.00buy
2026-10-079d8f9a372cc50.7.22.00buy