Developers
Inside the tools you code in.
Xovris in your terminal and the API – one engine.
XovrisOn its own
- A lit square is a feature people use today
- Newest: Open pages Xovris built and use them
Every feature in Developers, strongest first.
What fixes and prevents a problem comes first. Type to find one, or open a plan to see only its own.
Nothing here matches those words yet. Xovris notes the words, with no address and no cookie, so what is missing gets written.Ask Xovris instead
Lit: live and workingOpen: Xovris is still working on it
Open pages Xovris built and use them
The home page and the build page open two pages Xovris's own builder made, byte for byte, each beside the request that made it.
Limit a key to the sites you choose
An API key can be limited to what it may do and which domains, sites and servers it may touch, and Xovris enforces both on every call.
Every app Xovris builds is security-checked
Each build is checked for exposed keys, data access rules, unsafe code and vulnerable packages, and its server is tested by a stranger trying to get in.
Apps Xovris builds are safe by default
A new app's data is its owner's alone until they share it, prices come from the server, and an app with exposed data does not go live.
Nothing destructive without a checkpoint and your go
Xovris never takes down or overwrites an app's database, sign-in, files or payments without your go, keeps a checkpoint, and undoes it in one step.
Code review knows every deprecated Node API
Code review flags calls Node has deprecated, from Node's own published list, kept current by itself.
Ask about a pull request of any size
Ask about any pull request, however large, and Xovris reads every file it needs to answer.
API keys that never expire, made safe
An API key can be set never to expire wherever leaked keys are scanned for; where they are not, Xovris says so and keeps an end date.
Limit a key to your own addresses
An API key can be limited to the IP ranges you list, and every call from anywhere else is refused.
Every call a key made, listed
See every call an API key made, newest first, with the rule that refused any of them; a renewed key keeps its history.
Review steps done for you
When a review line hands you a step, such as replacing a dead link, Xovris carries it out itself.
Tools found on any package index
A package index beyond the seven Xovris knows is met through its own protocol when the maker's own page names it.
Secrets in your code found inside Xovris itself
Every code review runs an open-source secret scanner built into Xovris - 27 rules with entropy checks - so a leaked key is caught before it is merged.
CircleCI and Jenkins connected
Connect CircleCI or Jenkins beside your Git host and Xovris reads their build results and logs when a review or fix needs them.
Xovris inside your code editor
The Xovris extension runs in the most widely used code editors, so reviews and fixes appear where you write code.
Your build and tests worked out, never asked
Xovris works out how to build and test a repository from a bare clone, without asking you how.
Git submodules kept current too
Xovris keeps git submodules up to date like every other dependency, with the pointer change made as an ordinary pull request.
Filter findings on every axis at once
Narrow a review's findings by severity, category, kind, effort, file, status and source in one command, for example npx xovris findings --severity critical --category security.
A merge queue that keeps your main branch green
Hand Xovris a list of green pull requests through the API and it merges them in an order that keeps your main branch green.
Run the reviewer inside your own network
Companies can run Xovris's code reviewer and its proven fixes self-hosted inside a network with no route out.
Security findings mapped to OWASP and CWE
Every security finding in a code review carries its OWASP Top 10 and CWE Top 25 class, and a repository's findings can be reported by either list.
Reviews grouped by what a change does, with a spend cap
A review groups related edits by what they do, and on GitLab, Bitbucket or Azure DevOps it reads the spend cap you set in .xovris.yaml before any work begins.
Code fixes proved for every input, not one example
Beside the test that fails before and passes after, a code fix can be proved by a property over all inputs - a fix that only passes the example is refused.
Every candidate code fix is rehearsed first
Before a code fix is offered, Xovris rehearses every candidate in a sandbox copy and keeps only one that passes.
Reviews show what a change reaches
For a large change, the review lists its files in reading order, sums up each layer and shows everything the change can reach - every importing file and service.
Reviews follow your repository's own rules
Xovris reads the guideline files in your repository, such as AGENTS.md, applies each one only to the folder it lives in, and names it in the review.
Review settings live in your repository
Set how Xovris reviews your code in a .xovris.yaml file - path instructions, pattern rules and more - and share one central configuration across repositories.
Hand Xovris a coding job in plain words
From the API, say the change in plain words - fix the failing discount test. Xovris works it out in a checkout of its own, proves it with a test red before and green after, the suite, the build, the type check and the linters, and opens a pull request; it never opens one it has not proved, and the copy is deleted the moment the result is read.
The other areas
Words on this page, in plain English
Each technical word this page uses, said simply.
- Program-to-program connection (API, APIs)
- A way for one program to ask another for information or to do something, without a person clicking through a website.
- Plain-text settings (YAML)
- A common way of writing settings as indented lines of names and values.