Installation

There is no installation: rebar runs through npx, without writing a line into the repository it audits. What you install is the gate, and only in a project that wants one.

Audit a repository that already exists
Nothing is installed and nothing is written. You get a scoreboard, and the exit code tells you whether it passed: 0 passed, 1 failed, 2 invalid target, 127 the checker itself broke.
```
$npx github:Navesz/rebar .
```
Audit the security of that same repository
A different binary from the same package — hence the -p. Without it npx runs the format checker and you audit the wrong thing while believing you audited.
```
$npx -p github:Navesz/rebar rebar-security .
```
Start a project already on the right side of the line
Creates a static Next app with the gate inside, hooks, CI on a Windows and Linux matrix, and an MCP server that serves the rules to whatever AI opens the project.
```
$npx github:Navesz/rebar novo padaria-do-ze
```
Arm the gate in the project you just created
The hook does not come armed in a clone: without core.hooksPath the file sits on disk and git never runs it. The gate would look installed and verify nothing.
```
$npm run install-hooks
```
Run the whole sequence before you commit
It is the same command CI runs. Local and CI drifting apart is the defect that turns a gate into a green badge.
```
$npm run verify
```

PreviousDocs NextUsage

Audit a repository that already exists

Audit the security of that same repository

Start a project already on the right side of the line

Arm the gate in the project you just created

Run the whole sequence before you commit