Skip to main content

Codebase Statistics

Track the growth of the AILANG codebase over time. These metrics demonstrate the scale of AI-assisted development.

Loading codebase statistics...

What These Numbers Mean​

Lines of Code​

The AILANG project consists of multiple components:

  • Go Production Code: The compiler, runtime, type system, and CLI
  • Go Test Code: Comprehensive test suites with ~60% test-to-production ratio
  • AILANG Examples: Working examples and standard library
  • TypeScript/React: Documentation website and Collaboration Hub UI
  • Shell Scripts: Build automation, CI/CD, and development tools
  • Documentation: Design docs, guides, and reference material

Token Estimation​

The token count estimates how much context an AI model would need to "understand" the entire codebase. This is calculated at ~4 characters per token (typical for code).

Why this matters:

  • Modern AI models have context windows of 128K-200K tokens
  • The AILANG codebase (~4M tokens) requires strategic context management
  • This is why we use design docs, skills, and focused prompts

AI-Assisted Development​

AILANG is developed with Claude Code, demonstrating:

  1. Rapid iteration: 1,400+ commits in a few months
  2. Comprehensive documentation: Design-first approach with 160K+ lines of design docs
  3. High test coverage: Automated testing ensures reliability
  4. Sustainable pace: AI assistance enables consistent progress

Historical Tracking​

The timeline chart shows codebase growth across versions. Each data point is captured automatically during CI/CD builds.

What drives growth:

  • v0.3.x: Core language features (types, effects, modules)
  • v0.4.x: Monomorphization and polymorphism
  • v0.5.x: AI evaluation framework (M-EVAL-LOOP)
  • v0.6.x: Developer experience and tooling

Methodology​

Statistics are generated by tools/generate_codebase_stats.sh:

  1. Count lines using wc -l across all source files
  2. Exclude vendor, node_modules, and build artifacts
  3. Estimate tokens at ~4 characters per token
  4. Git statistics from repository history
  5. History preserved in codebase_stats.json

The script runs automatically during website deployment, ensuring metrics stay current.

Source Code: generate_codebase_stats.sh | Data File: codebase_stats.json