The hosted service
watchdep is offered as a hosted service: you sign up, get your own workspace, and invite the people you work with. The service has not opened yet; when it does, its address will be on this site. This page says how it works, and how it keeps every workspace’s data apart from every other’s.
The hosted service is the watchdep server running in its hosted mode. Like every watchdep server, it never reads source code, never holds write access to a repository and never runs a package manager.
Signing up and verifying the address
- The sign-up page takes a workspace name, your name, your email and a password (12 to 72 characters). It creates your account and your own workspace with you as its owner, signs you in, and emails a link to verify your address.
- Signing up with GitHub or Google creates the account from the provider’s verified email, already verified, with a workspace named after you.
- Until your address is verified, every screen says so in deep orange, with “Send it again”. The link works for two days, and only for the address it was sent to.
- An unverified account cannot accept an invitation.
- Creating an account from an invitation link does not verify the address, since whoever invited you can see the link: you are sent a verification email.
- Signing in with GitHub or Google never lands in an unverified account with the same email: sign in with its password (or reset it) first, then link the provider in Settings, My sign-in.
Attempts are limited: sign-up to 5 in 10 minutes from one address, sign-in to 10 in 3 minutes, and two-step sign-in codes to 6 in 3 minutes.
Several workspaces
A person may belong to several workspaces, by invitation or by creating more. The workspace name in the title bar opens a list of the others and, on a hosted copy, “New workspace”. Choosing one switches every screen to it. You can switch only into a workspace you belong to.
Roles are per workspace: you may be the owner of one and a viewer in another.
Deleting a workspace
Only the owner can delete a workspace, from Settings, Workspace, by typing its name exactly. Everything in the workspace goes: applications, parts, tokens, inventories, findings and their places, decisions, the log, code checks, pull request records, deployments, alerts, settings, the webhook, GitHub installations, invitations and memberships. People keep their accounts and their other workspaces.
The log of every other workspace stays append-only: the database refuses to delete a log entry unless its own workspace is being deleted.
How workspaces are kept apart
Every record belongs to a workspace, and nothing reads across them.
- Every screen, API call and search reads through the current workspace: the signed-in person’s, or the token’s for the API.
- Every record that belongs to a workspace carries a guard. Inside a request, a record of another workspace refuses to load, so a query that forgot to ask for the current workspace answers “not found” instead of showing someone else’s data.
- A test requests every screen that takes an id, with every method, as a member of another workspace, and requires “not found” from each and no change anywhere.
- Shared public data (advisories, the OSV mirror, CISA KEV, EPSS, end of life dates, early warnings, source health) holds nothing about any workspace. The status bar shows the same for everyone.
- API tokens read their own workspace only, and an agent reads only the workspace it was connected to.
GitHub on a hosted copy
A hosted copy never creates a GitHub App from the screen. It uses the operator’s App, given in the environment, and each workspace installs it on its own GitHub accounts. An installation belongs to the workspace that claimed it, through a link signed for that workspace and person; one already claimed by another workspace stays there. A part can be linked only to a repository its own workspace’s installation can see. See Connecting GitHub.
Webhooks on a hosted copy
A workspace’s webhook is resolved before every post. On a hosted copy, an address on a private, loopback or link-local network is always refused, whatever an owner ticked, so a workspace’s webhook cannot reach into the operator’s own network. See Alerts.
What stays the same
The hosted server, like every copy, never reads source code, never holds write access to a repository and never runs a package manager. Inventories come from the CLI or from the dependency files the GitHub App fetches; the code check and fix pull requests run in your own CI.