{"repo":"0-Shimanshu/ADIUVARE","free":true,"listed":false,"github":"https://github.com/0-Shimanshu/ADIUVARE","clone":"git clone https://github.com/0-Shimanshu/ADIUVARE.git","description":"A smart, dynamic risk-scoring security layer that lives inside your Python web apps (FastAPI, Flask, Django). It provides flexible protection and real-time visibility without the rigidness of traditional web filters.","language":"Python","stars":28,"topics":["ai","api-gateway","api-rest","api-wrapper","devtools","django","fastapi","flask","python","web-development"],"license":"Apache-2.0","category":"api-integrations-sdks","readme_excerpt":"Adiuvare Score and stop risky API requests before they reach your FastAPI, Flask, or Django handlers. Stateful request inspection, adaptive scoring, runtime controls, and local audit visibility - without shipping traffic into a separate platform first. Adiuvare is an in-process security layer for Python APIs. It sits inside your app, inspects requests before your handlers run, and combines fast hard checks with a softer scored review pipeline. That lets you reject obviously hostile traffic early, keep inspecting the requests that still pass, and leave a local audit trail behind every decision. The same runtime can then be inspected locally through the adv CLI and the TUI. It is a good fit when you want middleware-level protection, request scoring, operator controls, and runtime visibility in one place, with SQLite by default and Redis available when you need a different backend. --- Table of Contents - What problem it solves - Risk scoring, not rule filters - Installation - License - Quick start - What it looks like - Common usage - Configuration - Current scope - Payload coverage - Docs - Contributors What problem it solves Most teams start with request filters that look simple and feel reasonable: That approach breaks down quickly. - A legitimate request can get blocked just because it contains suspicious text. - Slight formatting changes can slip past brittle pattern checks. - A trusted identity and a brand-new identity get treated the same way if the current request looks","default_branch":null,"files":null,"tree":[],"storefront":"/r/0-Shimanshu","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/0-Shimanshu/ADIUVARE/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}