No reviews yetBe the first to leave a review for API Security Scanner PRO
Maker
π
Hey everyone!
I just released v1.2.0 of my API Security Scanner - a professional desktop application I built as part of my Bachelor's thesis at MEPhI (National Research Nuclear University, Moscow).
This major update reworks the payment system, improves the UI, and makes the project ready for a much wider audience!
What it does:
Scans OpenAPI 3.1, Swagger 2.0, and Postman collections for vulnerabilities
49+ security rules based on OWASP API Security Top 10
Generates detailed PDF/HTML reports with charts
Available as a native macOS .app (no Python installation needed)
π₯ What's New in v1.2.0:
β DeFi (Solana + USDT) & Boosty: Switched from TON to the more stable Solana/USDT network. Added Boosty for hassle-free payments for Russian users.
β Instant Licensing: Automatic key generation right after payment (no manual waiting!). Added an "Enter Key" button for manual input.
β Better Docs & Stability: Fully bilingual README (RU/EN) and fixed all payment-related confirmation bugs.
Technical highlights:
Built with Python + PyQt5 for the GUI (with an improved UI in v1.2.0)
YAML-based rules engine (easy to extend)
Docker & CLI support for CI/CD integration
Seamless crypto/fiat payment integration for global license management
Why I built this: I wanted to create a practical tool that combines API security testing with modern, frictionless payment systems. The new Solana/USDT and Boosty integrations allow users from any country to purchase and activate licenses instantly.
Congrats on the thesis project, sounds like a solid foundation. One thing that would make this way more useful for me: adding a VS Code extension or at least a JSON Schema validation step before the scan runs, so I can catch malformed specs early. Right now I imagine it just bombs out mid-scan and I'd have no idea if my spec is even valid.
Report
Maker
@meltemxfphΒ Great point! Right now, the scanner expects a valid specification and failing midβscan is indeed a painful experience.
We're planning to add JSON Schema validation for OpenAPI / Swagger files as an optional flag (e.g., --validate-spec), so you can catch malformed specs before running the full scan.
Also, we've already started building a VS Code extension that will highlight errors and provide autocomplete for our YAML rule syntax. We're aiming for a beta release soon β would love your feedback once it's ready.
Report
cool that this came out of a bachelor's thesis at MEPhI, the yaml-based owasp rules are actually super useful and i like that you can drop it into ci/cd. the ton payment thing is kind of unexpected for a security tool but honestly interesting
Report
Maker
@tanermyzrΒ Glad you find the YAML OWASP rules useful! As for TON β we chose blockchain payments to automate licensing and make it transparent for teams. It's just a payment mechanism, not part of the scanner itself. Your thoughts are super helpful as we continue refining the tool.
If you have any specific rule suggestions or features you'd like to see, let us know!
Hey everyone!
I just released v1.2.0 of my API Security Scanner - a professional desktop application I built as part of my Bachelor's thesis at MEPhI (National Research Nuclear University, Moscow).
This major update reworks the payment system, improves the UI, and makes the project ready for a much wider audience!
What it does:
Scans OpenAPI 3.1, Swagger 2.0, and Postman collections for vulnerabilities
49+ security rules based on OWASP API Security Top 10
Generates detailed PDF/HTML reports with charts
Available as a native macOS .app (no Python installation needed)
π₯ What's New in v1.2.0:
β DeFi (Solana + USDT) & Boosty: Switched from TON to the more stable Solana/USDT network. Added Boosty for hassle-free payments for Russian users.
β Instant Licensing: Automatic key generation right after payment (no manual waiting!). Added an "Enter Key" button for manual input.
β Better Docs & Stability: Fully bilingual README (RU/EN) and fixed all payment-related confirmation bugs.
Technical highlights:
Built with Python + PyQt5 for the GUI (with an improved UI in v1.2.0)
YAML-based rules engine (easy to extend)
Docker & CLI support for CI/CD integration
Seamless crypto/fiat payment integration for global license management
Why I built this:
I wanted to create a practical tool that combines API security testing with modern, frictionless payment systems. The new Solana/USDT and Boosty integrations allow users from any country to purchase and activate licenses instantly.
GitHub: https://github.com/MariaPruteanu/api-security-scanner
π₯ Download (macOS): https://github.com/MariaPruteanu/api-security-scanner/releases/latest
π¦ How to Update:
git pull origin main && git checkout v1.2.0 or just download the latest archive from the release page!
Would love your feedback on the security rules and the new payment flow! What other features would you like to see?
#CyberSecurity #APISecurity #OWASP #Python #OpenSource #Solana #Web3
Congrats on the thesis project, sounds like a solid foundation. One thing that would make this way more useful for me: adding a VS Code extension or at least a JSON Schema validation step before the scan runs, so I can catch malformed specs early. Right now I imagine it just bombs out mid-scan and I'd have no idea if my spec is even valid.
@meltemxfphΒ Great point! Right now, the scanner expects a valid specification and failing midβscan is indeed a painful experience.
We're planning to add JSON Schema validation for OpenAPI / Swagger files as an optional flag (e.g., --validate-spec), so you can catch malformed specs before running the full scan.
Also, we've already started building a VS Code extension that will highlight errors and provide autocomplete for our YAML rule syntax. We're aiming for a beta release soon β would love your feedback once it's ready.
cool that this came out of a bachelor's thesis at MEPhI, the yaml-based owasp rules are actually super useful and i like that you can drop it into ci/cd. the ton payment thing is kind of unexpected for a security tool but honestly interesting
@tanermyzrΒ Glad you find the YAML OWASP rules useful! As for TON β we chose blockchain payments to automate licensing and make it transparent for teams. It's just a payment mechanism, not part of the scanner itself. Your thoughts are super helpful as we continue refining the tool.
If you have any specific rule suggestions or features you'd like to see, let us know!