Skip to content
footnote Docs
Install

Security

What is scanned on every change, what leaves the service, and where to report a security problem.

What is scanned

The scans run on every pull request, on main and every night, whatever changed, because a new advisory can fail an unchanged lockfile. A change cannot merge until they pass.

ScanWhat it checks
SignaturesThe registry signature of every installed package, with npm audit signatures
OSV-ScannerEvery locked dependency against the OSV database, with reviewed exceptions
gitleaksEvery commit, for secrets and for files from a private profile

What leaves the service

  • To a model. With MODELS=live, Ask and the test runs send the model provider you choose the chat, the items they read and their owners’ names, never an e-mail address. Without it, scripted models answer and nothing is sent. What leaves this computer has the whole list, and who receives it for each provider.
  • To the tools you connect. A connector reaches only the hosts it declares, over https, and only reads: nothing is written back to the tool. See Connector security.
  • To agents. An agent reads only published context: a person’s agent only what that person may read, and an access key only what everyone may read. See Connect an agent by hand.

Report a problem

Report a security problem privately, never in a public issue: the security policy says how, what to include and what happens next.

Private profiles

Trying it on your own company’s data, keep it in a private profile, so no file from it can reach the repository: see Private profiles.

The restore drill

The drill that proves a backup restores is in Back up, restore and upgrade.