neosloc archive

Repositories /

lodash/lodash

https://github.com/lodash/lodash · commit 2b5e6f7399a7 · evaluated 2026-10-07 with neosloc 0.8.0 · JSON

0.67 integrability index over 3 applicable dimensions
none surfaces
$269k → $161k classic COCOMO → neosloc value (60% survives)
buy make / buy = 96.36 over 3 years

Dimensions

Interface surface 0 absent Not yet: A programmatic surface exists (routes, a CLI or a library).

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

  • next: L1 A programmatic surface exists (routes, a CLI or a library). (no service, CLI, library or frontend detected)

none ladder · level 0

  • ✗ L1 A programmatic surface exists (routes, a CLI or a library). no service, CLI, library or frontend detected
Contract stability n/a Not applicable: no service, cli, library, desktop or format surface.

Can integrators rely on it not changing under them?

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 n/a Not applicable: no service or cli or library or desktop surface.

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

Embeddability n/a Not applicable: no service or cli or library or desktop surface.

Can another system run and compose it without a human?

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 n/a Not applicable: no service or cli or library or desktop surface.

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

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. (86% of modules fit 32k tokens; 2 files over 12k; 0% of code is typed (< 70%))

all ladder · level 2

  • ✓ L1 A README and some tests. README.mdtest/asset/test-ui.js 6 test files
  • ✓ L2 CI runs the tests; applications pin dependencies (libraries and zero-dependency projects are exempt). .github/workflows/browser-testing.yml.github/workflows/ci-bun.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. 86% of modules fit 32k tokens; 2 files over 12k; 0% of code is typed (< 70%)
  • ✗ 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

1,170,071 output + 29,251,775 input tokens on anthropic:claude-opus-5-5 ≈ $46.

13.0 agent-hours · 284.9 human days (11.7 steering + 273.2 rediscovering history).

$221,519 over 3 years

Buy (adopt as is)

60 min to running (via –) + 1945 min to first use (via none).

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

$2,299 over 3 years

Buying wins below $73,073 per year. How this is estimated.

Classic COCOMO vs neosloc value

Classic COCOMO (sloccount)

8.93 KSLOC → 23.9 person-months over 8.4 months.

$269k

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

neosloc value (neoCOCOMO)

Reproduce with agents: 5.1 PM (×0.21 of classic; 75% of behaviour captured by tests, contract and docs).

Rediscover uncaptured history: 13.0 PM (723 fixes in 7518 commits by 275 authors).

× leverage 0.83 (integrability) × obsolescence 0.95.

$161k (14.3 PM)

What survives

60% of the classic figure

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

How the value is estimated.

History

2026-10-07: 0.672026-10-07: 0.672026-10-07: 0.672026-10-07: 0.67
EvaluatedCommitneoslocIndexMake or buy
2026-10-072b5e6f7399a70.8.00.67buy
2026-10-072b5e6f7399a70.7.40.67buy
2026-10-072b5e6f7399a70.7.30.67buy
2026-10-072b5e6f7399a70.7.20.67buy