Today, rebuff SDK consists of :

1. A first class TypeScript SDK which houses the code for all 4 layers of defense. 3 detection layers that occur prior to prompt submission (Heuristics, LLM-detection, VectorDB comparison) and 1 layer that uses canary tokens to validate if a prompt injection has occurred.

2. A Python SDK that must interact with a RESTful server (e.g. Rebuff Playground using the JS SDK) to do the 3 layers of detection mentioned above. The current python SDK does has the ability to add canary tokens, and detect if they've been leaked without the need for an external API call.

Going forward we're going to create a first class python SDK that has feature parity with the JS/TS SDK. We will move majority of the current python REST client within the server directory which will ultimately become its own repo (issue on this will be coming).