# What Programming Language Is Caveman Written In? A Technical Analysis > Discover the programming language behind Caveman. Primarily JavaScript on Node.js with a Python component for benchmarking. Learn more about this technical analysis. - Repository: [Julius Brussee/caveman](https://github.com/JuliusBrussee/caveman) - Tags: technical-analysis - Published: 2026-07-04 --- **Caveman is written primarily in JavaScript and runs on Node.js (version 18+), with a small auxiliary Python component for benchmarking.** The Caveman project by JuliusBrussee is a command-line tool that enforces terse, caveman-style communication rules in AI agents. If you are wondering what programming language Caveman is written in, the answer lies in the repository's core implementation and manifest files. The codebase is built as a Node.js application, leveraging JavaScript modules to handle installation, CLI commands, and agent integrations. ## JavaScript and Node.js Core Implementation The functional heart of Caveman is implemented in **JavaScript** targeting **Node.js** runtime environments. According to the JuliusBrussee/caveman source code, the [`package.json`](https://github.com/JuliusBrussee/caveman/blob/main/package.json) file explicitly declares the Node engine requirement with `"node": ">=18"`, ensuring compatibility with modern JavaScript features and APIs. The core implementation relies on standard Node.js modules for file system operations. In [`src/tools/caveman-init.js`](https://github.com/JuliusBrussee/caveman/blob/main/src/tools/caveman-init.js), the installer imports native Node modules using CommonJS syntax: - `require('fs')` for file system manipulation - `require('path')` for cross-platform path resolution These dependencies confirm that the project is not just browser-based JavaScript but a server-side Node.js application designed to interact with the local file system. ## Key Source Files and Architecture Understanding what programming language Caveman is written in requires examining the repository's file structure and entry points. ### package.json Configuration The [`package.json`](https://github.com/JuliusBrussee/caveman/blob/main/package.json) file serves as the project manifest and defines the runtime environment. It specifies the `caveman` binary as a JavaScript entry point, linking to [`bin/install.js`](https://github.com/JuliusBrussee/caveman/blob/main/bin/install.js) as the CLI executable. This configuration confirms that the primary language is JavaScript and the execution context is Node.js. ### Main Installer Logic (caveman-init.js) The [`src/tools/caveman-init.js`](https://github.com/JuliusBrussee/caveman/blob/main/src/tools/caveman-init.js) file contains the core installation logic written in plain JavaScript. This module handles writing the caveman rule files to supported agent directories. The code uses synchronous file operations and template literals to generate rule content: ```javascript const fs = require('fs'); const path = require('path'); const RULE_BODY = `Respond terse like smart caveman. ... Switch level: /caveman lite|full|ultra|wenyan`; ``` ### CLI Entry Points The [`bin/install.js`](https://github.com/JuliusBrussee/caveman/blob/main/bin/install.js) file acts as a thin wrapper that invokes the installer when users run the `caveman` command from their terminal. This architecture separates the CLI interface from the core logic while maintaining JavaScript as the single implementation language for the user-facing components. ## Auxiliary Python Components While the primary programming language is JavaScript, Caveman includes **Python** for specific auxiliary tasks. The [`benchmarks/run.py`](https://github.com/JuliusBrussee/caveman/blob/main/benchmarks/run.py) file contains Python helper scripts used for performance benchmarking. These scripts are not part of the core functionality but support development and optimization workflows. The Python components are strictly optional and do not affect the main CLI installation or rule management features. ## Installation and Usage Examples ### Running the CLI After installing via npm, the `caveman` command becomes available in your shell. The binary executes JavaScript code through the Node.js runtime: ```bash # Install globally npm install -g caveman # Initialize caveman rules in current repository caveman init # Display help documentation caveman --help ``` ### Invoking the Installer via Shell Script Users can also install Caveman directly without npm using the provided shell script, which downloads and executes the JavaScript installer: ```bash curl -fsSL https://raw.githubusercontent.com/JuliusBrussee/caveman/main/install.sh | bash ``` This shell script ultimately invokes the same JavaScript entry points defined in [`package.json`](https://github.com/JuliusBrussee/caveman/blob/main/package.json). ## Summary - **Caveman is written in JavaScript** and requires Node.js version 18 or higher to run. - The core logic resides in [`src/tools/caveman-init.js`](https://github.com/JuliusBrussee/caveman/blob/main/src/tools/caveman-init.js) and uses standard Node.js APIs like `fs` and `path`. - **[`package.json`](https://github.com/JuliusBrussee/caveman/blob/main/package.json)** defines the runtime requirements and CLI entry points, confirming the Node.js dependency. - **Python is used only for auxiliary benchmarking** in [`benchmarks/run.py`](https://github.com/JuliusBrussee/caveman/blob/main/benchmarks/run.py) and is not required for core functionality. - Installation methods include npm global install or direct shell script execution, both leveraging the same JavaScript codebase. ## Frequently Asked Questions ### Is Caveman written in TypeScript or JavaScript? Caveman is written in plain **JavaScript**, not TypeScript. The source files use CommonJS module syntax (`require` statements) and standard JavaScript without type annotations. The [`package.json`](https://github.com/JuliusBrussee/caveman/blob/main/package.json) does not list TypeScript as a dependency or build tool. ### Why does Caveman require Node.js 18 or higher? The [`package.json`](https://github.com/JuliusBrussee/caveman/blob/main/package.json) specifies `"node": ">=18"` to ensure compatibility with modern JavaScript features and security updates. Node.js 18 provides stable implementations of modern APIs that the file system operations in [`caveman-init.js`](https://github.com/JuliusBrussee/caveman/blob/main/caveman-init.js) rely upon, including improved path handling and promise-based file system methods. ### Can I run Caveman without installing Node.js? No, you cannot run the core Caveman functionality without Node.js. While you can install the tool via the shell script ([`install.sh`](https://github.com/JuliusBrussee/caveman/blob/main/install.sh)), that script ultimately executes JavaScript files that depend on Node.js runtime APIs. The only way to use Caveman without Node.js would be to manually implement the rule-writing logic in another language. ### Is the Python code in benchmarks required for installation? No, the Python code in [`benchmarks/run.py`](https://github.com/JuliusBrussee/caveman/blob/main/benchmarks/run.py) is completely optional and only used for development performance testing. The standard installation via `npm install` or the shell script does not execute or require Python. Caveman's CLI functionality depends solely on JavaScript and Node.js.