neosloc archive

Repositories /

neosloc/neosloc

https://github.com/neosloc/neosloc · commit 7c115da643ab · evaluated 2026-10-12 with neosloc 0.8.0 · JSON

2.88 integrability index over 8 applicable dimensions
cli, library surfaces · uses credentials
$131k → $20k classic COCOMO → neosloc value (15% survives)
buy make / buy = 4.68 over 3 years

Dimensions

Interface surface 4 exemplary [cli] The output format is specified by a JSON Schema.

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

  • next: [library] L2 The public API is delimited (__all__, an exports map, exported identifiers). (no __all__/exports defining the public API)

cli ladder · level 4

  • ✓ L1 Invocable non-interactively: no prompts, or prompts guarded by a TTY check or a --yes/--no-input option. no interactive prompts
  • ✓ L2 --help documents every option (at least 90% of options have help text). neosloc/cli.py options with help text
  • ✓ L3 Machine-readable output (--json/--format) and documented exit statuses. neosloc/cli.py 2 matchesdocs/json.md 1 match
  • ✓ L4 The output format is specified by a JSON Schema. neosloc/schema.py 2 matches

library ladder · level 1

  • ✓ L1 An importable, packaged API exists. pyproject.toml Python package neosloc
  • ✗ L2 The public API is delimited (__all__, an exports map, exported identifiers). no __all__/exports defining the public API
  • ✗ L3 The public API is statically typed (py.typed, type declarations, a typed language). no py.typed or type declarations
  • ✗ L4 An API reference is generated from the code (autodoc, mkdocstrings, typedoc, …). no generated API reference
Contract stability 2 partial A changelog exists and marks breaking changes.

Can integrators rely on it not changing under them?

  • next: L3 A deprecation mechanism is used in code (warnings, @deprecated, Deprecation/Sunset headers) or the API is versioned. (no deprecation mechanism or API versioning)

all ladder · level 2

  • ✓ L1 Releases are versioned (semver tags or versioned changelog sections). 12 semver tags, latest v0.8.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. no deprecation mechanism or API versioning
  • ✓ L4 Across tagged releases, no OpenAPI operation, CLI option or __all__ symbol was removed without first being deprecated. 12 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 3 solid [library] No output or log statement includes a credential.

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

  • next: [cli] L2 Credentials never need to be on the command line, and their environment variables are documented. (--auth-header takes a secret on the command line (visible in shell history and ps))
  • next: [library] L4 Several profiles or scoped credentials per target. (no credential profiles)

cli ladder · level 1

  • ✓ L1 Credentials can be supplied non-interactively (environment variables). neosloc/agentic/llm.py 1 match
  • ✗ L2 Credentials never need to be on the command line, and their environment variables are documented. --auth-header takes a secret on the command line (visible in shell history and ps)
  • ✓ L3 No output or log statement includes a credential. no credential in print/log statements
  • ✗ L4 Several profiles or scoped credentials per target. no credential profiles

library ladder · level 3

  • ✓ L1 Credentials can be supplied non-interactively (environment variables). neosloc/agentic/llm.py 1 match
  • ✓ L2 The credential environment variables are documented. README.md 1 matchdocs/evaluators.md 1 match
  • ✓ L3 No output or log statement includes a credential. no credential in print/log statements
  • ✗ L4 Several profiles or scoped credentials per target. no credential profiles
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 3 solid [cli] Documented exit statuses distinguish error classes, errors are JSON in JSON mode, and color is off when not a TTY.

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

  • next: [cli] L4 --dry-run, limits for long or costly operations (timeouts, budgets), and agent docs. (no --dry-run)
  • next: [library] L4 Agent docs, and examples that run as tests (doctests). (examples don't run as tests)

cli ladder · level 3

  • ✓ L1 Never blocks on a prompt when stdin is not a TTY. no interactive prompts
  • ✓ L2 Data on stdout, diagnostics on stderr, non-zero exit on failure. neosloc/log.py 11 matchesneosloc/errors.py 7 matches
  • ✓ L3 Documented exit statuses distinguish error classes, errors are JSON in JSON mode, and color is off when not a TTY. docs/json.md 1 matchneosloc/cli.py help text
  • ✗ L4 --dry-run, limits for long or costly operations (timeouts, budgets), and agent docs. no --dry-run

library ladder · level 3

Embeddability 4 exemplary [library] Optional features behind extras/features.

Can another system run and compose it without a human?

  • next: [cli] L4 Also shipped as a container image or a single binary. (no container image or binary)

cli ladder · level 3

library ladder · level 4

  • ✓ L1 Importable from source. pyproject.toml Python package neosloc
  • ✓ 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/release.yml 1 match 0 runtime dependencies
  • ✓ L4 Optional features behind extras/features. pyproject.toml 1 match
Extensibility 2 partial The docs show how to add behaviour through those seams (even in-tree).

Can behaviour be added without modifying the code?

  • next: L3 Out-of-tree extensions are discovered (entry points, a plugin directory, configuration) without editing the package. (extensions must be added inside the package)

all ladder · level 2

  • ✓ L1 Internal seams: a registry, registration function or plugin manager. neosloc/ladder.py 1 match
  • ✓ L2 The docs show how to add behaviour through those seams (even in-tree). docs/extending.md 3 matches
  • ✗ 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 3 solid [cli] Structured logs (e.g. --log-format json) or a machine-readable run summary.

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

  • next: [cli] L4 Tracing hooks (OpenTelemetry). (no tracing hooks)
  • next: [library] L2 Log levels are used meaningfully (at least two levels). (fewer than two log levels used)

cli ladder · level 3

  • ✓ L1 Meaningful exit statuses, and errors on stderr. neosloc/log.py 11 matchesneosloc/errors.py 7 matches
  • ✓ L2 Verbosity control for diagnostics (--quiet, --log-level, --debug). neosloc/cli.py 3 matches
  • ✓ L3 Structured logs (e.g. --log-format json) or a machine-readable run summary. neosloc/cli.py 1 matchneosloc/log.py 1 match
  • ✗ L4 Tracing hooks (OpenTelemetry). no tracing hooks

library ladder · level 1

  • ✓ L1 Logs through a standard logger namespace and never prints from library code. neosloc/log.py 1 match no print() in library code
  • ✗ 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; 1 files over 12k)

all ladder · level 2

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

Make or buy

Make with agents

276,119 output + 6,902,975 input tokens on anthropic:claude-opus-5-5 ≈ $11.

3.1 agent-hours · 2.4 human days (2.2 steering + 0.2 rediscovering history).

$1,896 over 3 years

Buy (adopt as is)

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

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

$405 over 3 years

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

Classic COCOMO vs neosloc value

Classic COCOMO (sloccount)

4.49 KSLOC → 11.6 person-months over 6.3 months.

$131k

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

neosloc value (neoCOCOMO)

Reproduce with agents: 1.7 PM (×0.14 of classic; 90% of behaviour captured by tests, contract and docs).

Rediscover uncaptured history: 0.0 PM (0 fixes in 22 commits by 1 authors).

× leverage 1.11 (integrability) × obsolescence 0.95.

$20k (1.8 PM)

What survives

15% of the classic figure

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

How the value is estimated.

History

2026-10-07: 2.882026-10-07: 2.882026-10-07: 2.882026-10-07: 2.882026-10-07: 2.882026-10-07: 2.882026-10-12: 2.88
EvaluatedCommitneoslocIndexMake or buy
2026-10-127c115da643ab0.8.02.88buy
2026-10-0721f4c243437c0.8.02.88buy
2026-10-079ea165a72ae70.7.42.88buy
2026-10-07fc297b7cd8120.7.32.88buy
2026-10-076306a22d93ab0.7.22.88buy
2026-10-0734cd14f8bb350.7.12.88buy
2026-10-07161ea8761e1f0.7.12.88buy