Sign in
An account is only for the features that need to know it is you. The index itself — every page, the dataset and the feeds — stays open without one.
Finish signing in
You opened a sign-in link. Press the button to sign in — opening the link alone does not.
Not open yet
Sign-in is not open yet. Nothing on this site needs an account.
Submit a repository for a check
We fetch your repository and list the Odoo modules in it. A submission is private by default — only you see it. A public repository can be published in the index as a whole; from a private one, submitted with a deploy key, you can publish chosen modules under Your modules.
We fetch the code and read the manifests right away — nothing from it is executed. The install test itself is a separate paid option that is not open yet.
First: is your repository public or private?
- Public (it opens in a browser without signing in): paste its address in the form below, choose Public repository and press Submit. That is all.
- Private: connect it with our deploy key — the four steps below, about two minutes. You need admin rights on the repository (on GitLab — the Maintainer role).
Private repository: connect in 4 steps
- Fill in the form below. Paste the repository address as the browser shows it, e.g.
https://github.com/owner/repo. Enter a branch only if you need one other than the default. Keep Deploy key selected and press Submit. - Copy the key. A line starting with
ssh-ed25519appears under the form. Press Copy key — it copies the whole line. The key is made for this one submission only. - Add the key to the repository on your hosting — read access only, do not allow write access:
- GitHub: open the repository → Settings tab → in the left menu, Deploy keys → Add deploy key. Title: anything, e.g.
allservices.one; Key: paste; leave Allow write access unticked; press Add key. GitHub shows a hint at the top of that page recommending GitHub Apps — you can skip it for this step. - GitLab: open the project → Settings → Repository → section Deploy keys → Add new key. Title: anything; Key: paste; leave Grant write permissions to this key unticked; press Add key.
- Bitbucket: open the repository → Repository settings → Access keys → Add key. Label: anything; Key: paste; save. Access keys are read-only by design.
- Codeberg: open the repository → Settings → Deploy keys → Add deploy key. Title: anything; Content: paste; leave Enable write access off; press Add deploy key.
- GitHub: open the repository → Settings tab → in the left menu, Deploy keys → Add deploy key. Title: anything, e.g.
- Come back here and press “Check access”. In a few seconds you see “fetched: commit …” and the list of modules found.
Closed the page before step 4? The key and the “Check access” button stay under Your modules.
“No access” after “Check access” usually means one of three things: the key went into a different repository; the key was pasted but not saved; the address in the form points to another repository (a fork, an old name). Fix it and press “Check access” again — there is no need to submit again. If you have no admin rights on the repository, ask its admin to add the key, or use a token (below).
No admin rights to add a key? Use a read-only token instead
GitHub — a fine-grained token for one repository, read-only:
- On GitHub open Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token.
- Resource owner: the account or organisation that owns the repository. Repository access: Only select repositories, and pick that one repository.
- Permissions → Repository permissions → Contents: Read-only. Leave everything else at No access (Metadata: Read-only is added by GitHub itself).
- Expiration: as short as possible — 7 days is enough for one check.
- Generate it, copy the token (it starts with
github_pat_) and paste it below.
Classic tokens (ghp_…) are refused: they cannot be limited to one repository. If the repository belongs to an organisation, an owner of that organisation may have to approve the token first.
GitLab: in the project open Settings → Access tokens → Add new token, role Reporter, scope read_repository only, with an expiry date. The token starts with glpat-. If project tokens are not available on your plan, a personal access token with only read_repository works too — but it can read all your projects, not one.
Tokens work for GitHub and GitLab only. For Bitbucket and Codeberg, use the deploy key.
What happens to the key and the token
The deploy key is ours, made for this one submission: we keep its private half encrypted on our server and delete it together with the submission. A token, if you choose one, is used once — at the moment you submit, to fetch the code — and is not stored anywhere; to fetch again you submit again. When you are done, remove the key or revoke the token on your side as well.
What we keep
Your email address as the provider has verified it, your display name and the provider’s account number. No password — there is none. The provider’s access token is used once to read your profile and is not stored. One essential cookie keeps you signed in; there are no tracking cookies. How we handle this is described in the privacy notice.
What it does today
Today an account does nothing except exist. Alerts about your own modules and private messages about a result come next, and this page will say so when they do. Signing in with GitHub and with Google using the same email gives you one account, not two.