# Caido: what the caido/caido repository actually contains > Caido is a web application security auditing proxy for pentesters and bug bounty hunters. The GitHub repository named caido/caido is not the proxy source: it holds releases, the roadmap, branding and scripts, while the product itself is distributed through the Caido dashboard and documented at docs.caido.io. **caido/caido** — 🚀 Caido releases, wiki and roadmap - Repository: https://github.com/caido/caido - Website: https://caido.io - Stars: 2,612 · Forks: 140 - Language: Shell - License: not declared - Published: 2026-09-28 · Updated: 2026-09-28 · Language: en - Canonical page: https://hysenlabs.com/projects/caido-caido ## What Caido is for, and who the repository is aimed at Caido describes itself as a tool that helps security professionals and enthusiasts audit web applications "with efficiency and ease". That places it in the same working category as an intercepting HTTP proxy: something you put between a browser or client and a target web application so you can observe and modify requests. The topics attached to the repository (bugbounty, pentesting, proxy, security, tool) point at the same audience: people doing authorised security testing, whether on a bug bounty programme or an internal engagement. The README frames the repository itself as a place to "get involved with the development of our software", and points readers to the roadmap for upcoming features. That framing matters. If you arrive expecting a source tree you can compile, the top-level layout tells a different story: .github/, README.md, SECURITY.md, brand/, prompts/ and scripts/. There is no application source directory listed. The repository is a distribution and coordination point, not the product's codebase. ## How releases, the dashboard and the roadmap fit together The mechanism visible in the repository is a release pipeline plus a pointer to a hosted account area. The README states that the project tries to release a new version at least once a month, and that those versions can be found in the releases section of the GitHub repository or in the Caido Dashboard at dashboard.caido.io. The recent release list supports the cadence claim: v0.58.0 on 2026-08-20, v0.58.2 on 2026-08-22, and v0.58.3 on 2026-09-04. The last push to the repository was on 2026-09-04, which lines up with the most recent release rather than indicating continuous source activity. Upcoming features are described on the roadmap, linked from the README through links.caido.io/roadmap. So the data flow for a user is: read the roadmap to see what is coming, download or update through the releases section or the dashboard, and read docs.caido.io for how to operate the tool. The GitHub repository is the announcement and artefact layer; the dashboard is the account and distribution layer. The README does not describe the proxy's internal architecture, request interception model, or storage format, so anything beyond the release and documentation pointers would be guesswork. ## Installing Caido and a first real use The README does not contain installation commands. It links to the website, the dashboard, the docs, the roadmap and the Discord community, and states that new versions appear in the releases section or in your Caido Dashboard. That means the authoritative install path is docs.caido.io, and the artefact source is the releases section of this repository. The README gives no command for listing or fetching releases, so the first step is to open the releases section of the repository in a browser and read the notes for the tag you intend to deploy. The most recent tag listed is v0.58.3, published on 2026-09-04. From there, follow the dashboard link at dashboard.caido.io to obtain the build, and docs.caido.io for the operating instructions. The README does not document a CLI, an installer flag, a default port or a certificate setup procedure, so any command beyond opening those pages would be invented rather than sourced. ## What the repository does not give you The clearest limitation is one of expectation. If you want to read the proxy's implementation, audit its request handling, or build it yourself, this repository will not help: the top-level entries are .github/, README.md, SECURITY.md, brand/, prompts/ and scripts/, and the README describes the repository as a place to follow development, not as the product source. The primary language listed for the repository is Shell, which is consistent with scripts and release automation rather than an application codebase. The licence is also unstated in the information available here, which is a real problem for anyone whose organisation requires a known licence before procurement. A second limitation is cadence versus stability. The release history shows three releases in about two weeks (v0.58.0, v0.58.2, v0.58.3), which is faster than the stated monthly target and means pinned versions age quickly. Finally, the README's own scope is narrow: it covers community, roadmap and release pointers, and it does not document rollback, downgrade paths, or what happens to your data between versions. If your workflow depends on a frozen, long-supported build, this is the wrong shape of project for you. ## Caido versus Burp Suite: the difference in approach The most common comparison people search for is Caido against Burp Suite, and the repository supports only a partial answer. Both are web application security proxies aimed at pentesters, and both sit between a client and a target so requests can be inspected and modified. The structural difference visible here is distribution and release rhythm. Caido publishes versioned releases through GitHub and a hosted dashboard, states an intent to ship at least monthly, and routes users to docs.caido.io for operating instructions. That is a hosted-account plus rapid-release model. Burp Suite is not described anywhere in this repository, so no claim about its licensing, extension model or release cadence can be made from these facts. What can be said is that Caido's repository is deliberately thin: releases, roadmap, branding and scripts. If you are choosing between proxies, the deciding evidence is not in this repository at all. It is in docs.caido.io and in the release notes for the specific version you would deploy. ## Maintenance, upgrade cost and licence questions Maintenance signals here are concrete. The repository is not archived, and the last push was on 2026-09-04, which is the same day as the v0.58.3 release. That pattern suggests the repository is updated as part of the release process rather than as a daily development surface. The README states the project tries to release at least once a month, and the recent tags show a faster pace in August and early September 2026. For an upgrade budget, that means version drift is the main cost: you should expect to re-check the releases section regularly and to read the notes for each tag rather than assuming a long support window. The repository does not state an end-of-life policy, a long-term support branch, or a downgrade procedure, so those are open questions to raise before standardising on a version. On licensing, the repository does not state a licence in the information available, and the README does not link a licence file. That is a gap rather than a conclusion: anyone who needs a known licence term should confirm it through the website or the dashboard before deploying, and treat the absence of a stated licence as a reason to ask rather than to assume permissive terms. Nothing here should be read as legal advice. ## Community, security reporting and where to ask The README points to a Discord community for users to connect and ask questions, linked through links.caido.io/www-discord. It also links the roadmap, the docs, the website and the dashboard, and notes that branding assets live under brand/ in the repository. For anything security-related, the repository carries a SECURITY.md at the top level, which is the conventional place for a vulnerability disclosure policy; the README itself does not restate those terms. That separation is worth noting: if you find a flaw in Caido itself, the README is not the channel it describes, and you should read SECURITY.md rather than opening a public issue. The prompts/ directory at the top level is not described in the README, so what it contains and how it is used cannot be stated from this repository. The practical takeaway is that the repository is a hub of pointers, and each pointer (docs, dashboard, Discord, SECURITY.md) carries a different kind of information. ## Conclusion Caido suits security professionals and enthusiasts who audit web applications and want a proxy that ships a new version roughly monthly, with release notes and binaries reachable from the repository's releases section or the Caido Dashboard. Anyone expecting to clone caido/caido and build the proxy from source will not find that here, because the repository holds releases, the roadmap, branding and scripts. Before adopting it, verify the licence terms, confirm the current version in the releases section, and check docs.caido.io for the installation path that matches your platform. The repository's SECURITY.md is the place to look for how vulnerabilities in Caido itself should be reported. ## FAQ ### What is Caido used for? Caido is described in its README as a tool that helps security professionals and enthusiasts audit web applications with efficiency and ease. The repository topics group it with bug bounty, pentesting, proxy and security tooling. ### How do I install Caido? The README does not give installation commands. It points to the releases section of the repository and to the Caido Dashboard for new versions, and to docs.caido.io for documentation, so the install steps live in the docs rather than in this repository. ### Is Caido better than Burp Suite? The repository does not compare the two. What it does show is Caido's distribution model: versioned releases through GitHub and the Caido Dashboard, a stated intent to release at least monthly, and documentation at docs.caido.io. ### How much does Caido cost? The repository does not state pricing or licence terms. The README links to the website and the Caido Dashboard, which are the places to check for that information. ### What is Caido? Caido is a tool aimed at security professionals and enthusiasts for auditing web applications, distributed through versioned releases on GitHub and the Caido Dashboard, with documentation at docs.caido.io. ## Sources - [caido/caido on GitHub](https://github.com/caido/caido) - [Issues](https://github.com/caido/caido/issues) - [Project website](https://caido.io) - [README](https://github.com/caido/caido/blob/main/README.md) - [Releases](https://github.com/caido/caido/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/caido-caido