Security
What the scan stores, and what it does not.
These notes describe the product as it runs. They are not a certification, a penetration-test report, or legal advice.
The scan reads. It does not write to your repo.
GitHub access is Contents read, Metadata read, Pull requests read, and Checks write. A scan uses a short-lived installation token. The token and the file text are not stored. Synlex does not commit or push. A zip upload is the path that does not install the app.
Workspace data is isolated in the database.
Each workspace’s rows are separated with row-level security. That is database-enforced isolation. It is not a claim of per-tenant encryption keys.
Releases are signed and versioned.
An owner or compliance lead signs after a fresh authenticator code or passkey. The manifest covers the version, the commit, the plan digest, and each document hash. The algorithm is Ed25519. The public keys, current and retired, each with the dates it was in use, are at /.well-known/synlex-keys.json when a signing key is configured.
You review everything before it ships.
Generate can preview a draft. Accept is what stores it, and only if the draft still names the plan’s evidence. A release is refused while an answer is missing or a document is unaccepted or stale.
Public keys, when signing is configured: /.well-known/synlex-keys.json
Package licence lookups
When a lockfile declares no licence for a public package, the worker asks these public services for it.
deps.dev, Google’s Open Source Insights
api.deps.devAsked first, for npm, Cargo, Go, RubyGems, PyPI, and Gradle (Maven) packages.
npm’s registry
registry.npmjs.orgAsked only for an npm package version when deps.dev lists no licence for it.
- The worker sends the name and version of each public package a scanned repository uses, and nothing else.
- No personal data, code, or repository name is sent. A package from a private registry, a git dependency, or a local folder is never sent.
- Answers are cached. A version a service answered is not asked about again, and one it did not know is asked again after a week.
- These services get no personal data, so they are not on the sub-processor list.
- Workspace owners and admins can turn the lookups off for a project, or list private package names to leave out.
Not claimed
- Synlex is not a law firm. A draft is not legal advice, and it is not a statement that you are fully compliant.
- No SOC 2, ISO, or penetration-test report is published.
- Workspace isolation is row-level security in the database. There is no per-tenant encryption key, private network, or microVM.
- Pull-request check runs are not available yet. A push to the default branch is what queues a scan.
- The public key file is an empty list until a signing key is configured on that host.