Skip to content

LiudasJan/Rentgen

Repository files navigation

🔬 Rentgen

👉 Landing page: rentgen.io 👉 Download: Latest Release

Rentgen - Automation before automation. Finding API bugs when you have no tests.


Why Rentgen

Most API tools focus on how to send requests. Rentgen focuses on what your API does under pressure.

From a single known-good request, Rentgen automatically checks:

  • HTTP behavior
  • error handling
  • security headers
  • edge cases that cause real production bugs
  • performance insights

This is behavior-first API testing, not scripting.


What Rentgen does

  • Generate dozens of API tests from one request
  • Detect misleading HTTP statuses (401 vs 403, 400 vs 413, etc.)
  • Catch security and caching issues before production
  • Test HTTP, WebSockets (WSS), and Protobuf APIs
  • Run locally — your data never leaves your machine

Real bugs, not theory

Rentgen has already found real issues in production APIs, including:

  • broken payload size handling (DoS risk)
  • missing cache-control on private data
  • incorrect authorization responses
  • unsafe CORS configurations

📖 Read real API Stories → rentgen.io/api-stories


Get started (30 seconds)

  1. Download the latest Release
  2. Open Rentgen
  3. Import a cURL
  4. Run tests

That’s it. If something fails just copy bug report and share with a team.

🎬 Demo

Rentgen Demo


Who this is for

  • QA engineers
  • API developers
  • security-conscious teams
  • anyone tired of “it works on my machine”

Philosophy

Boring bugs cost the most.

Rentgen exists because the most expensive API bugs are the ones nobody thinks to test.

About

Automation before automation. Finding API bugs when you have no tests

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages