Private code.
Public GitHub.
Find the leak first.
When your company's source code, internal designs, infrastructure details or secrets end up in someone's public repository, repoSnare finds them, even years later. You get verified findings, preserved evidence and a clear report, so your team can respond.
Findings
Your proprietary code or secrets found in public repositories.
| Repository | Severity | |
|---|---|---|
| rk-dev-archive/pay-backup Proprietary code · high confidence | Critical | |
| jlee-notes/archive Proprietary code · high confidence | Critical | |
| contractor-io/client-work Code and secrets · high confidence | High | |
| dk-deploy-scripts/staging-setup Secret exposure · high confidence | High | |
| old-laptop-sync/notebooks Proprietary code · medium confidence | Medium |
Product preview with fictional data. The interface may change before launch.
It's rarely an attack. It's usually an accident.
Source code, internal designs and infrastructure details that belong inside your company end up in someone's public GitHub account, and they stay there until somebody notices.
The personal backup
A developer copies a project, docs and all, to their own account "just in case," and the repository is public by default.
The contractor's portfolio
Work done for you gets published to impress the next client, along with your configs, diagrams and credentials.
The fork that went public
An internal tool or design repository is forked outside your organization and keeps its full history.
From "is it out there?" to a report you can act on.
Agree what's yours
Company and former names, brands, domains, project names, public accounts and suppliers. We help you set up the profile.
We run your assessment
repoSnare searches years of public GitHub history for your identifiers, including repositories that have since been deleted, wherever their content can still be found.
You get findings and a report
Each finding is analyzed and verified before it reaches you, with preserved evidence and a report that states exactly what was searched.
Respond, then keep watching
Assign owners, track remediation and re-check exposed repositories. Continue with monitoring to catch new leaks as they happen.
Every leak, in one calm place.
See what's open, what's new and what needs an owner, then drill into the evidence behind each finding.
Overview
What needs your attention and what monitoring found.
New findings and observations last 30 days
Needs attention 4
- 2 critical findings have no owner yet
- Remediation overdue: dk-deploy-scripts/staging-setup, 3 days past your deadline
- Repository deleted after capture. The sealed copy is kept.
- Historical scan complete. Report version 2 is ready.
Open findings and observations See all findings
| Repository | Tier | Severity |
|---|---|---|
| rk-dev-archive/pay-backup | Finding | Critical |
| jlee-notes/archive | Finding | Critical |
| contractor-io/client-work | Finding | High |
A report leadership can read
Every assessment ends with a report: an executive version for leaders and a technical version for the people fixing things.
- What was found, why it's yours and what to do next
- What was searched, and any limits, stated plainly
- Numbered versions, so an earlier report never changes
Hunt › Historical scans › A-0007
Historical exposure assessment
Agreed scope · started Nov 3 · finished Nov 12
Unavailable or not covered
- 2 repositories deleted before capture. Content recovered for 1.
- 1 repository could not be captured. Listed in the report.
- Every candidate investigated within the agreed scope.
Report versions 2
| v2 · Nov 14 | Executive PDF |
| Technical PDF | |
| v1 · Nov 12 | 5 files |
Evidence behind every finding
Each finding shows exactly why it's yours and what was exposed.
- Each match checked and marked verified
- Secrets shown as fingerprints and never tested or used
- A sealed snapshot that stays even if the repository is deleted
Findings › Finding
rk-dev-archive/pay-backup
Evidence (4 of 4 verified)
Each citation is re-checked against the sealed copy.
- 1. Internal package nameVerifiedFile
src/ledger/settle.go· Lines 12 - 2. Project nameVerifiedFile
README.md· Lines 3 - 3. Company email domainVerifiedCommit
4e1c9a2 - 4. Internal hostnameVerifiedFile
config/prod.yaml· Lines 41
Secrets found
Shown as a fingerprint and a location, never the value. repoSnare never tests whether a credential works.
| Detector | Where |
|---|---|
| Cloud access key | Current files |
| Database password | Only in the history |
Actions
LabelNeeds review SeverityCritical (assessed) ReviewRecord a remediation stepResolveMark as duplicate Check repository nowExport this finding Legal holdPlace legal holdProduct preview with fictional data. The interface may change before launch.
Start with an assessment. Stay with monitoring.
Both are scoped and quoted up front, so you know what's included before any work starts.
Historical exposure assessment
A one-time search of public GitHub history for your company's code and sensitive material.
- Your agreed identifiers, searched across all available history
- Verified findings with preserved evidence
- Executive and technical versions of the report
- A response window with live monitoring included
- Hands-on onboarding and a walkthrough of the results
Ongoing public monitoring
A continuous watch for new leaks of your work, after an assessment or on its own.
- New public activity checked as it happens
- Open findings re-checked over time
- Alerts by email and signed webhooks
- Historical searches as your profile changes
- The same findings, evidence and response workflow
More than keys
Source code, internal designs and infrastructure details, plus any secrets that leaked along with them.
Honest about coverage
Every assessment says what was searched, what was completed and where content was unavailable. "No findings" is never presented as proof of no exposure.
Delivered where you work
Findings arrive by email and signed webhooks, with the full record in the web console.
A security product should be secure first.
We hold the evidence of your leaks, so we built repoSnare like a vault.
Your own encryption keys
Every customer's data is encrypted under its own key and kept strictly separate.
SSO, MFA and roles
Single sign-on, required multi-factor sign-in and roles that control who can see secrets or download evidence.
Complete audit trail
A tamper-evident log of every action, including any Techscape support session, that you can always see.
We never use what we find
Leaked credentials are locked away and never tested or used, and only people you authorize can reveal them.
See what's already out there.
We're onboarding a small group of early customers. Tell us about your organization and we'll scope an assessment with you.