ayoubfathi/leaky-paths
A collection of special paths linked to common sensitive APIs, devops internals, frameworks conf, known misconfigurations, juicy APIs ..etc. It could be used as a part of web content discovery, to scan passively for high-quality endpoints and quick-wins.
Topics
Explore related topics
Jump into the topic listings this repository belongs to.
Join the conversation
Reviews · Questions · Posts
Share what you know about leaky-paths — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Write or update your review
Explain what worked, what broke down, and what another team should know before adopting leaky-paths.
Project Q&A
Questions and answers
Browse implementation threads tied directly to ayoubfathi/leaky-paths. Each question links through to the full answer page.
Be the first to ask how teams run leaky-paths in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
Posts tagged with the same topics
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses leaky-paths — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post