Rename CLI binary to 'cants'; keep codeanalyzer-typescript package name

The invoked executable is now 'cants' (CodeANalyzer TypeScript): CLI program
name (commander), package.json bin, the bun --compile outfile, the bundled
wheel binary (__init__.py _BINARY_NAME), the GitHub Release asset name, and all
README usage examples.

The PyPI distribution and Python import stay 'codeanalyzer-typescript' /
codeanalyzer_typescript -- consistent with the codeanalyzer-python/-java
siblings, and avoiding the 'cants' name collision on npm. Distribution name and
binary name are independent, so no PyPI rename, retire, or sdk-pin-name change.

Bump to 0.2.0 for the user-visible command rename.

Author: rahlk

.github/workflows/release.yml

@@ -1,6 +1,6 @@
 name: Release (binaries + Python wheels)
 
-# Builds the self-contained codeanalyzer-typescript binary for every supported
+# Builds the self-contained cants binary for every supported
 # platform and publishes:
 #   1. the raw binaries as GitHub Release assets (for analysis_backend_path /
 #      $CODEANALYZER_TS_BIN / download-on-first-use use cases), and
@@ -100,7 +100,7 @@ jobs:
             python -m zipfile -e "$whl" "$tmp"
             bin="$(find "$tmp/codeanalyzer_typescript/_bin" -type f ! -name '.gitignore')"
             ext=""; [[ "$bin" == *.exe ]] && ext=".exe"
-            cp "$bin" "../../release-bins/codeanalyzer-typescript-${plat}${ext}"
+            cp "$bin" "../../release-bins/cants-${plat}${ext}"
           done
           ls -lh ../../release-bins
 

README.md

@@ -25,7 +25,7 @@ be resolved as phantom (external) nodes; pass `--no-build` to reuse an already-p
 curl -fsSL https://bun.sh/install | bash
 ```
 
-## Building `codeanalyzer-typescript`
+## Building `cants`
 
 Clone the repository and install dependencies:
 
@@ -38,7 +38,7 @@ bun install
 Compile a standalone native binary (no Bun/Node required to run it afterward):
 
 ```bash
-bun run build      # → dist/codeanalyzer-typescript
+bun run build      # → dist/cants
 ```
 
 You can also run the analyzer directly from source without compiling:
@@ -55,15 +55,15 @@ TypeScript/JavaScript projects.
 ### Basic Usage
 
 ```bash
-codeanalyzer-typescript --input /path/to/typescript/project
+cants --input /path/to/typescript/project
 ```
 
 ### Command Line Options
 
-To view the available options, run `codeanalyzer-typescript --help`:
+To view the available options, run `cants --help`:
 
 ```text
-Usage: codeanalyzer-typescript [options]
+Usage: cants [options]
 
 CLDK TypeScript analyzer — emits the canonical analysis.json
 (symbol table + resolver call graph).
@@ -93,28 +93,28 @@ Options:
 
 1. **Basic analysis (symbol table + call graph):**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project
+   cants --input ./my-ts-project
    ```
 
    This prints the analysis to stdout as compact JSON. To save it instead, use `--output`:
 
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --output /path/to/analysis-results
+   cants --input ./my-ts-project --output /path/to/analysis-results
    ```
 
    The results are written to `analysis.json` in the specified directory.
 
 2. **Change output format to msgpack:**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --output /path/to/analysis-results --format msgpack
+   cants --input ./my-ts-project --output /path/to/analysis-results --format msgpack
    ```
 
    This saves the results to `analysis.msgpack`, a binary format that is more compact for
    storage and transmission.
 
 3. **Deeper analysis with CodeQL enrichment (experimental):**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --analysis-level 2
+   cants --input ./my-ts-project --analysis-level 2
    ```
 
    Every run produces a symbol table **and** a call graph. At level 1, edges come from the
@@ -123,15 +123,15 @@ Options:
 
 4. **Incremental analysis of specific files:**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --target-files src/a.ts src/b.ts
+   cants --input ./my-ts-project --target-files src/a.ts src/b.ts
    ```
 
    Restricts the analysis to the named files, reusing the cached analysis for the rest of
    the project.
 
 5. **Force a clean rebuild with a custom cache directory:**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --eager --cache-dir /path/to/custom-cache
+   cants --input ./my-ts-project --eager --cache-dir /path/to/custom-cache
    ```
 
    `--eager` rebuilds the analysis cache from scratch. If `--cache-dir` is omitted, the cache

package.json

@@ -1,15 +1,15 @@
 {
   "name": "codeanalyzer-typescript",
-  "version": "0.1.1",
+  "version": "0.2.0",
   "description": "CLDK TypeScript analyzer — emits the canonical CLDK analysis.json (symbol table + resolver-based call graph) via ts-morph.",
   "type": "module",
   "module": "src/index.ts",
   "bin": {
-    "codeanalyzer-typescript": "dist/codeanalyzer-typescript"
+    "cants": "dist/cants"
   },
   "scripts": {
     "start": "bun run src/index.ts",
-    "build": "bun build ./src/index.ts --compile --outfile dist/codeanalyzer-typescript",
+    "build": "bun build ./src/index.ts --compile --outfile dist/cants",
     "typecheck": "tsc --noEmit"
   },
   "license": "Apache-2.0",

packaging/python/README.md

@@ -17,15 +17,15 @@ TypeScript/JavaScript projects.
 ### Basic Usage
 
 ```bash
-codeanalyzer-typescript --input /path/to/typescript/project
+cants --input /path/to/typescript/project
 ```
 
 ### Command Line Options
 
-To view the available options, run `codeanalyzer-typescript --help`:
+To view the available options, run `cants --help`:
 
 ```text
-Usage: codeanalyzer-typescript [options]
+Usage: cants [options]
 
 CLDK TypeScript analyzer — emits the canonical analysis.json
 (symbol table + resolver call graph).
@@ -55,28 +55,28 @@ Options:
 
 1. **Basic analysis (symbol table + call graph):**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project
+   cants --input ./my-ts-project
    ```
 
    This prints the analysis to stdout as compact JSON. To save it instead, use `--output`:
 
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --output /path/to/analysis-results
+   cants --input ./my-ts-project --output /path/to/analysis-results
    ```
 
    The results are written to `analysis.json` in the specified directory.
 
 2. **Change output format to msgpack:**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --output /path/to/analysis-results --format msgpack
+   cants --input ./my-ts-project --output /path/to/analysis-results --format msgpack
    ```
 
    This saves the results to `analysis.msgpack`, a binary format that is more compact for
    storage and transmission.
 
 3. **Deeper analysis with CodeQL enrichment (experimental):**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --analysis-level 2
+   cants --input ./my-ts-project --analysis-level 2
    ```
 
    Every run produces a symbol table **and** a call graph. At level 1, edges come from the
@@ -85,15 +85,15 @@ Options:
 
 4. **Incremental analysis of specific files:**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --target-files src/a.ts src/b.ts
+   cants --input ./my-ts-project --target-files src/a.ts src/b.ts
    ```
 
    Restricts the analysis to the named files, reusing the cached analysis for the rest of
    the project.
 
 5. **Force a clean rebuild with a custom cache directory:**
    ```bash
-   codeanalyzer-typescript --input ./my-ts-project --eager --cache-dir /path/to/custom-cache
+   cants --input ./my-ts-project --eager --cache-dir /path/to/custom-cache
    ```
 
    `--eager` rebuilds the analysis cache from scratch. If `--cache-dir` is omitted, the cache
@@ -134,7 +134,7 @@ Apache 2.0 — see [LICENSE](./LICENSE).
 
 ## About this package
 
-This distributes the compiled `codeanalyzer-typescript` binary as a set of
+This distributes the compiled `cants` binary as a set of
 platform-specific Python wheels, published to PyPI as **`codeanalyzer-typescript`**.
 The CLDK Python SDK depends on this package and calls
 `codeanalyzer_typescript.bin_path()` to locate the analyzer binary. The binary is

packaging/python/build_wheels.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Build platform-tagged Python wheels for the codeanalyzer-typescript binary.
+# Build platform-tagged Python wheels for the cants (codeanalyzer-typescript) binary.
 #
 # For each target: cross-compile the binary with Bun, build a (pure) wheel with
 # hatchling, then retag it from `py3-none-any` to the matching platform tag with
@@ -74,7 +74,7 @@ for entry in "${TARGETS[@]}"; do
   clean_bin
 
   ( cd "$REPO_ROOT" && bun build ./src/index.ts --compile --target="$target" \
-      --outfile "$BIN_DIR/codeanalyzer-typescript$ext" )
+      --outfile "$BIN_DIR/cants$ext" )
 
   # Build a pure wheel (py3-none-any), then retag to the platform.
   python -m build --wheel --no-isolation -o "$HERE/dist" "$HERE"

packaging/python/src/codeanalyzer_typescript/__init__.py

@@ -1,6 +1,6 @@
-"""Prebuilt ``codeanalyzer-typescript`` backend binary for CLDK.
+"""Prebuilt ``cants`` (codeanalyzer-typescript) backend binary for CLDK.
 
-This package carries the platform-specific, self-contained ``codeanalyzer-typescript``
+This package carries the platform-specific, self-contained ``cants``
 executable (built from this repo with ``bun build --compile``) and exposes its
 filesystem path. CLDK's Python SDK depends on this package and calls
 :func:`bin_path` to locate the analyzer, exactly as it imports ``codeanalyzer-python``
@@ -22,11 +22,11 @@
 
 __all__ = ["bin_path", "__version__"]
 
-_BINARY_NAME = "codeanalyzer-typescript" + (".exe" if sys.platform == "win32" else "")
+_BINARY_NAME = "cants" + (".exe" if sys.platform == "win32" else "")
 
 
 def bin_path() -> Path:
-    """Return the absolute path to the bundled ``codeanalyzer-typescript`` binary.
+    """Return the absolute path to the bundled ``cants`` binary.
 
     Raises:
         FileNotFoundError: if the wheel for this platform did not include a binary
@@ -38,7 +38,7 @@ def bin_path() -> Path:
 
     if not path.exists():
         raise FileNotFoundError(
-            f"Bundled codeanalyzer-typescript binary not found at {path}. "
+            f"Bundled cants binary not found at {path}. "
             "This usually means there is no prebuilt wheel for your platform; "
             "build the binary with `bun build --compile` and point CLDK at it via "
             "analysis_backend_path or $CODEANALYZER_TS_BIN."

src/cli.ts

@@ -6,7 +6,7 @@ import type { AnalysisOptions, OutputFormat } from "./options";
 export function parseArgs(argv: string[]): AnalysisOptions {
   const program = new Command();
   program
-    .name("codeanalyzer-typescript")
+    .name("cants")
     .description("CLDK TypeScript analyzer — emits the canonical analysis.json (symbol table + resolver call graph).")
     .requiredOption("-i, --input <path>", "project root to analyze")
     .option("-o, --output <dir>", "output directory for analysis.json (omit ⇒ compact JSON to stdout)")