A little order for your scripts

Good scripts.
Less searching.

Find the right script, see what it does, and follow what it depends on. A shared catalog with a fast CLI and a keyboard-first terminal browser.

Get started Read the source

Built in Rust / Linux x86-64 / Works offline

THE SCRIPT CATALOG01 / FIND
Discover. Inspect. Connect.
One native binaryRead-only browsingNo central web serviceNo client model downloads

From “somewhere on the shared drive”

To exactly what
you were looking for.

Scripts accumulate. Context gets lost. Scat brings names, content, owners and relationships into one place, without moving your files or requiring Git.

01 / DISCOVER

Search beyond the filename.

Search script content and metadata. Filter by language, owner or tag; find function names and declared input or output files.

02 / UNDERSTAND

Get the whole picture.

Preview source, inspect checkout status and compare revisions. Follow dependencies, symlinks and related scripts without losing your place.

03 / KEEP MOVING

Stay in your terminal.

Browse with the keyboard or use the CLI in your own tools. Export selected fields as JSON or search CSV when you need to take results further.

A small catalog. A quick look.

Try finding something.

This browser demo searches a few fictional scripts. The real scat searches your indexed files from the CLI or TUI.

SAMPLE CATALOG
scat search --limit 50

A lightweight illustration, not the scat search engine. The terminal app also has full-text ranking, regex search and dependency navigation.

Made for shared environments

A shared index.
A local experience.

A nightly job builds the SQLite catalog on your indexing host. Engineers browse it read-only, with a host-local cache to keep ordinary queries off the network share.

Built for offline Linux and RHEL workflows. No central web service, open ports or runtime language installation needed on clients.

See how it fits together
01Indexing hostScan & publish nightly
02scripts.sqliteOne shared catalog
03Your CLI & TUIRead-only · cached locally

Your next command

Get your bearings.

Start with the Linux x86-64 binary and an existing catalog from your team. Publishing a new catalog is a separate administrator workflow.

01 / GET SCAT

Grab a build.

Download scat-linux-x86_64-musl from a successful main-branch run and extract the binary. GitHub may require sign-in to download artifacts.

Browse build artifacts ↗

No tagged releases yet. Optional RPM packaging and site-specific installation are covered in the deployment guide.

02 / POINT IT AT YOUR CATALOG
chmod +x scat
export SCAT_DB=/shared/scripts.sqlite
./scat search backup
./scat tui
Read the quick start →

A few useful details

Before you dive in.

Does scat run or change my scripts?

Ordinary search and browsing read the indexed catalog. Catalog builds and vc operations are separate, explicitly invoked administrator actions. Opening the TUI does not start an indexer or service.

Can I use it over SSH or without internet access?

Yes. The client reads your catalog offline and supports terminal glyph and color overrides for constrained sessions. Clipboard forwarding depends on your terminal. See theSSH and terminal guide.

Which systems does it target?

The main scat binary targets Linux x86-64. RHEL 8, 9 and 10 are the intended support matrix, with UBI userspace checks in CI. Actual host-policy and mount validation is site-specific; see thedeployment guide. Windows is not supported by the main client.

Where do I report a problem?

Run scat doctor for read-only diagnostics, review the output for paths and host identifiers before sharing, andopen an issue. For command help, run scat --help or press F1 in the TUI.