Security and privacy across the lifecycle
Two questions matter here:
- What does Niro itself read, keep and send?
- How can Niro help a security review of your own code?
What Niro reads, keeps and sends
- Reads: the source, config and text files in the folders you add. It never opens real
.envfiles, private keys, key stores or tool credential files. - Keeps: the graph and the build state, on your computer, in files only your user account can read.
- Sends: a small set of things, each listed in What leaves your machine.
The tools your agent uses answer from the graph on your computer. In Niro's own words: "Niro's tools answer your assistant from the graph on this machine and never send the contents of your files."
More detail:
- Secrets and masking: how secrets are hidden before anything is shown or sent.
- Coverage audit: the one place where small pieces of code leave the computer.
- Where things are stored: every file Niro writes.
Using Niro in a security review
Niro can help in three ways:
- List the attack surface.
find_api_endpointslists every route your code serves.find_outbound_http_callslists every call it makes to other services. - Follow the data.
list_data_resourcesandget_data_resource_usageshow which code reads and writes each table. - Check reach before a fix.
get_blast_radiusshows what a security fix will touch.
One limit to keep in mind: a route built while the program runs, from values computed at that time, is not in the graph. Niro lists only routes written as fixed text, and says so in the answer.