Skip to content

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.

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.

  • 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.

Scan a repository you already have.

You review the draft before anything is accepted.

Start free