# Basta

> Updated 2026-09-23 · type: tool · category: productivity-knowledge · status: active · rev 1

Basta is a Rust-engined CLI that detects unused files, exports, imports and declarations in JS/TS and Python codebases.

- Open source: yes (MIT)
- Self-hostable: yes
- Pricing model: free
- Best for: A developer or platform engineer on an AI-native team who wants to keep a JS/TS or Python codebase lean by finding and removing provably dead files, exports and imports as part of code review or CI.
- Last verified: 2026-09-23

- **Canonical:** https://gtmstacker.com/registry/tool/basta/
- **Source:** [github · kucherenko/basta](https://github.com/kucherenko/basta)
- **Tags:** productivity-knowledge, project-ops, self-hostable, developer-tooling, code-quality, cli
- **Repository:** https://github.com/kucherenko/basta

## Is Basta open source?

Yes, Basta is open source under the MIT license.

## How much does Basta cost?

Basta is free to use.

## Can I self-host Basta?

Yes, Basta can be self-hosted (the source is available under the MIT license).


---

MIT-licensed dead-code detector with a Rust engine that finds unused files, exports, imports and declarations across JavaScript/TypeScript and Python. It is a command-line developer tool for codebase hygiene — you run it against a repo and it reports what is provably unreferenced so it can be safely removed. Rust is the analysis engine, not a target language; the languages it analyzes are JS/TS and Python. Actively maintained (npm v0.3.0 published 2026-09-22).

## Provenance

- MIT (OSI-open, confirmed in repo and npm metadata); 15 stars, last push 2026-09-22 (active); npm v0.3.0 published 2026-09-22; installs as a CLI and detects unused files, exports, imports and declarations across JS/TS and Python via a Rust engine (WebFetch 2026-09-23, github.com/kucherenko/basta).
- Two corrections honored: jscpd.dev is the author's separate project, not this tool's homepage; and Rust is the engine, not a scanned language.
- Curated from the GTM Stacker signal registry (2026-09-23 pass); license/facts independently verified 2026-09-23.

## Why it matters for a GTM stack

The honest framing: this is not a GTM tool. It is codebase-hygiene tooling for the people building the GTM stack — the same class as the registry's "drop" sandbox entry. AI-native teams that ship fast accumulate dead files, orphaned exports and stale imports quickly, and that cruft slows every later change and every agent that reads the repo. Basta is the mechanical answer: a fast, Rust-engined pass that flags what is provably unreferenced across JS/TS and Python so it can be pruned in review or CI. If your GTM engine is software you maintain, keeping that codebase lean is the leverage; if you are buying GTM tools rather than building them, this one is out of scope.