Most teams have secrets in git they've forgotten about — hardcoded credentials, leaked API keys, committed .env files, and rotated-but-not-revoked tokens. This is secret sprawl: credentials scattered across repos and history, some still live, most of it noise. You suspect they're there. You don't know which are live exposures versus noise. A read-only assessment turns those findings into a prioritized report: rotate today, rotate this week, log and ignore.
Your secret scanning is probably already running, producing a wall of findings nobody opens. I do a read-only assessment across your organization's repositories, classify every finding by real risk — not just "secret found" — and deliver a prioritized remediation report:
No false-positive dump. No changes to your systems. No tooling to install or maintain.
Two ways to engage. Both are read-only, fixed scope, no tooling to install, and delivered as a prioritized remediation report a busy engineering leader can actually act on.
The method behind both is in two field notes: why triage is the part nobody sells, and a real assessment run on the practice’s own codebase.
Establish your current risk baseline. Read-only, fixed scope — the full scan, the triage, and a prioritized remediation report.
Keep your secret hygiene clean after the baseline. Recurring monitoring and rotation guidance — we flag the credential and API key rotations that matter — so new exposures get caught before they age.
Access is granted via a read-only GitHub token scoped to contents:read and metadata:read at the organization level. Tokens are time-bound and revocable by you at any moment.
A mutual NDA is signed before any access is granted.
I confirm liveness with read-only identity calls to a credential's own provider — never by reading your secret values. I never read or store secret values from your vaults.
For cautious teams, a client-run variant is available: you run the scan inside your environment and send me the raw findings.
Harvey Ramer has spent more than 20 years building and architecting software — from solo client engagements to systems that have to stay up. Unrotated is that engineering discipline turned on a problem nobody owns: credentials committed to version control that get found and never rotated — the unrotated credentials and secret debt no one will touch.
He scans read-only, verifies liveness without ever reading your secret values, and hands you a prioritized report a busy engineering leader can actually act on. You're hiring an engineer who treats your exposures like live incidents — because until a human confirms otherwise, that's the safe read.