Please report security issues privately rather than in a public issue, through GitHub's private vulnerability reporting.
Include what an attacker can do, the steps to reproduce, and the app version. You should get an initial response within a week.
Apilator is a desktop client. There is no telemetry. Apart from the HTTP requests you
make, the only network traffic the app starts on its own is the update check: five seconds
after start and every six hours after that, it fetches the release manifest
(latest.json) from this project's GitHub releases. It carries nothing from your requests,
collections or environments; like any request, it shows GitHub your IP address. See
Updates.
Stored on disk, under %LOCALAPPDATA%\Apilator\:
- open tabs and request history — request details only; response bodies are not kept
- saved collections
- environments, excluding the values of variables marked secret
The credential on a request's Auth tab — the Basic password, the Bearer token or the JWT secret — is written to these files encrypted with Windows DPAPI for your user account, not in the clear. Copied to another machine or another Windows account, the files load without those credentials.
Stored in the Windows Credential Manager:
- proxy passwords
- environment variables marked secret
Not stored at all: response bodies beyond the current session.
Apilator checks GitHub for new releases in the background and offers them; it never downloads or installs anything on its own. Update packages are signed with a minisign key whose public half is compiled into the app, so a package that was not signed by this project is rejected before anything is installed.
The installer itself is not code-signed with a Windows certificate, so SmartScreen warns on first run. That is about the installer's provenance, not the update mechanism.
TLS verification can be turned off. It is on by default. When you turn it off, every response fetched over an unverified connection is marked in the response header, because a connection that is not authenticated can be intercepted.
Requests go out as you write them. Variables are substituted into the URL, headers, query parameters, body and auth fields, so a secret in an environment variable will appear in whatever request references it. That is the point, but it means a request shared from history or a collection can carry one.
Exported collections leave out Auth tab credentials, but nothing else. The password, token or JWT secret is blanked in an export. A token typed straight into a header, a query parameter or the body is exported as written. Use a secret environment variable if you intend to share the collection.