Fitting in
The editor API
A small JSON API for reviewing a file before it is committed.
What it takes
A set of files as text, and it returns credentials and code findings against them. Nothing is cloned and nothing is stored. Tokens are scoped and expire.
Why it exists
The cheapest finding is the one caught before it is committed, because nothing has entered the history yet.
The plugin is built on it
The editor plugin calls this endpoint and no other, so anything you write against it behaves the way the plugin does. See In your editor.
What it does not do
It reviews what you send it and nothing more. It has no idea what your repository holds, which is the scan's job, and a review is never written down: no finding, no exception, no history.
Every feature page carries one of those. The comparison page scores the same ground against five products people pay for, including the rows that go against us.