1. What you are agreeing to
These terms cover your use of Atlas, a local application that analyses backend source code and sends HTTP requests. By using it you accept them. If you do not, do not use it.
2. What you may use it on
Only on code and systems you own or have permission to work with. Atlas can read any directory you point it at and send requests to any host you name, so the responsibility for choosing those targets is entirely yours. Using it to probe systems you are not authorised to test is a breach of these terms and may be unlawful where you are.
3. Accounts
An account is optional and exists only to attribute comments and feedback. You are responsible for keeping your password secret and for what happens under your account. Use an address you control, and tell whoever operates your instance if you believe your account has been accessed by someone else.
4. Your content stays yours
Source code, analysis results, captured responses, environment values and comments are yours. Nothing in these terms transfers any right in them, and because they are written to your own disk, we have no access to them and no ability to act on them.
5. What the analysis is, and is not
The analyser reads code without running it. That makes it fast and repeatable, and it also makes it approximate. It can miss a route registered dynamically, misread an unusual pattern, or report an endpoint as unprotected when a gateway in front of it enforces authentication.
Security findings are prompts to go and look, not a certification that anything is safe. Do not treat a clean report as evidence that an application has no vulnerabilities, and do not treat this tool as a substitute for review or penetration testing.
6. Requests you send
The request panel sends real HTTP requests to real servers. A request that deletes something will delete it. Check the method, the target and the environment before you press send, particularly when a production base URL is selected.
7. Availability
Atlas is provided as is. The software may change, features may be added or removed, and no uptime or fitness for a particular purpose is promised. Optional integrations depend on third parties — GitHub, or a mail webhook you configure — and those can fail independently.
8. Liability
To the fullest extent the law allows, the authors are not liable for lost data, lost profits, or any indirect or consequential damage arising from use of the software, including damage caused by a request you chose to send or by relying on an analysis result.
9. Changes
These terms may be updated. The date at the top of this page reflects the current version, and continuing to use Atlas after a change means you accept it.