What problem does it solve? During authorized security testing, organizations often unknowingly expose source code, configuration files, and credentials on public code hosting platforms. Manually searching for these leaks is slow and unsystematic, and testers frequently miss high-value exposures like database credentials in config files. ## Core Features & Use Cases - Fingerprint-Driven Search: Converts tech stack fingerprints (framework patterns, cookie names, error messages, page titles) into targeted search queries for GitHub, Gitee, and Google dorks. - High-Value Target Prioritization: Focuses on config files (application.yml, .env, settings.py), database credentials, API keys, CI/CD configs, and Docker environment variables. - Secondary Confirmation Workflow: Verifies candidate leaks by comparing directory structures, API routes, and frontend JS variable names before saving links, without downloading the code. - Use Case: While testing an authorized target running Spring Boot, extract a unique error string from its responses, search GitHub for matching code, and discover a leaked application.yml containing live database credentials. ## Quick Start Analyze the target's tech fingerprint and search GitHub and Gitee for leaked source code, config files, and credentials matching its unique identifiers.
