JustHandled Labs
// Developer Tools

Gitignore Coverage Preflight

Check supplied repository paths and ignore patterns for uncovered or already tracked sensitive-looking files.

What problem does Gitignore Coverage Preflight solve?

A plausible ignore file can still miss a nested environment file, private key, credential export, or negation that re-includes sensitive material.

Use it to

What it returns

A representative input and result

fixture-backed sample
input {"paths":["src/app.js",".env"],"patterns":[".env"],"tracked_paths":[]}
result READY; .env is covered by the supplied pattern and no sensitive tracked path is present.

Access and approval boundaries

Known limitations

Questions

Does it change or upload anything?

No. It reads supplied local evidence and writes only to the selected output directory.

Is this an AI judgment?

No. The packaged checker is deterministic and applies documented rules to the supplied input.

What does a ready result mean?

It means no automated finding was produced. The responsible owner still reviews the original source and decides what to do.

How does malformed input behave?

Invalid JSON, duplicate identifiers, missing required arrays, and invalid core values fail closed.

Can I audit the result?

Yes. Every finding carries a stable code, record identifier, severity, source, and message.

Gitignore Coverage Preflight keeps proof and approval boundaries visible.

The listing includes the tested package, realistic samples, declared permissions, and known limitations.

Get Gitignore Coverage Preflight on Agensi