Sample work · Code & Bugs
Secrets scanning: Finding credentials in code without exposing them
A demo repository with invented, intentionally fake credentials. The scanner finds them in multiple files, reports them without plain text, generates .gitignore and .env.example, and reports nothing when the code is clean. Real keys are not present in any part.
Sample work (demo), not a client job. Built as a trial task with invented example data; the check figures below come from the automatic test run and are not polished.
What was built
- Findings with file and line, plain text masked
- Control test: clean repository with no false positives
- .gitignore and .env.example generated
- Repository and keys invented
How it was checked
Automatic test run on 2026-10-31, taken from the log (test data invented, figures measured):
- Demo-repo: 5 built-in fake leaks found in 4 files, no false positives, report without plain text, .gitignore and .env.example generated
- 12 checks, control tests passed
Limits
What this sample does not cover, so nobody expects more:
- Sample scan finds known key formats, not freely chosen passwords
- Only the account owner can revoke found values; we do not touch customer accounts
- The Git history is checked only with customer read access; rewriting history is a separate agreement
Something like this for your business?
Describe briefly what you need. You get a fixed price before I start; nothing happens without your yes.