neosloc archive

Repositories /

psf/requests

https://github.com/psf/requests · commit 611c6162cbc4 · evaluated 2026-10-07 with neosloc 0.8.0 · JSON

2.00 integrability index over 7 applicable dimensions
library surfaces
$138k → $13k classic COCOMO → neosloc value (9% survives)
buy make / buy = 76.16 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 requests
  • ✓ L2 The public API is delimited (__all__, an exports map, exported identifiers). src/requests/__init__.py __all__
  • ✓ L3 The public API is statically typed (py.typed, type declarations, a typed language). src/requests/py.typed py.typed
  • ✓ L4 An API reference is generated from the code (autodoc, mkdocstrings, typedoc, …). docs/conf.py 1 match
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). 162 semver tags, latest v2.34.2
  • ✓ L2 A changelog exists and marks breaking changes. HISTORY.md marks breaking changes
  • ✓ L3 A deprecation mechanism is used in code (warnings, @deprecated, Deprecation/Sunset headers) or the API is versioned. src/requests/utils.py 5 matchessrc/requests/auth.py 4 matches
  • ✓ 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 0 absent Not yet: Errors are specific exception types, and library code never calls sys.exit.

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

  • next: L1 Errors are specific exception types, and library code never calls sys.exit. (library code exits the process: setup.py)

library ladder · level 0

Embeddability 4 exemplary Optional features behind extras/features.

Can another system run and compose it without a human?

library ladder · level 4

  • ✓ L1 Importable from source. pyproject.toml Python package requests
  • ✓ L2 Installable as a package (a package manifest). pyproject.toml package manifest
  • ✓ L3 Published to a public registry, with at most 10 runtime dependencies. .github/workflows/publish.yml 2 matches 4 runtime dependencies
  • ✓ L4 Optional features behind extras/features. pyproject.toml 1 match
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: src/requests/certs.py, src/requests/help.py)

library ladder · level 0

  • ✗ L1 Logs through a standard logger namespace and never prints from library code. library code prints: src/requests/certs.py, src/requests/help.py
  • ✗ L2 Log levels are used meaningfully (at least two levels). fewer than two log levels used
  • ✗ 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; 0 files over 12k)

all ladder · level 2

  • ✓ L1 A README and some tests. README.mdtests/compat.py 15 test files
  • ✓ L2 CI runs the tests; applications pin dependencies (libraries and zero-dependency projects are exempt). .github/workflows/close-issues.yml.github/workflows/codeql-analysis.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; 0 files over 12k
  • ✗ L4 No import cycles, and agent docs (AGENTS.md, CLAUDE.md, llms.txt). no agent docs (AGENTS.md, CLAUDE.md, llms.txt)

Make or buy

Make with agents

292,449 output + 7,311,225 input tokens on anthropic:claude-opus-5-5 ≈ $11.

3.2 agent-hours · 1.9 human days (1.9 steering + 0.0 rediscovering history).

$1,532 over 3 years

Buy (adopt as is)

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

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

$20 over 3 years

Buying wins below $504 per year. How this is estimated.

Classic COCOMO vs neosloc value

Classic COCOMO (sloccount)

4.73 KSLOC → 12.3 person-months over 6.5 months.

$138k

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

neosloc value (neoCOCOMO)

Reproduce with agents: 1.2 PM (×0.1 of classic; 100% of behaviour captured by tests, contract and docs).

Rediscover uncaptured history: 0.0 PM (669 fixes in 4883 commits by 794 authors).

× leverage 1 (integrability) × obsolescence 0.95.

$13k (1.2 PM)

What survives

9% of the classic figure

0% 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-07611c6162cbc40.8.02.00buy
2026-10-07611c6162cbc40.7.42.00buy
2026-10-07611c6162cbc40.7.32.00buy
2026-10-07611c6162cbc40.7.22.00buy