tdurieuxandClaude Fable 5.1
a02e83e48c
"Report an issue" in the navbar read like a way to report an anonymized
repository, and it opened a blank GitHub issue instead of the template
that asks reporters to confirm the issue is about the service. The user
menu offered "Default settings" and "Logout" with no hint of what lives
behind them, and the Claim page was unreachable from any menu.
The settings page never loaded quotas (the bars stayed in their striped
loading state), mixed serif checkbox labels with sans forms, used
Bootstrap alert colours, and described options in jargon ("Proxy mode",
"Github page", "Line of code").
- Navbar: "Report a bug" links to the issue template with a tooltip that
names the service; the user menu shows who is signed in and lists
Settings, Claim an anonymization, Report a bug, Source code, Sign out,
each with a one-line hint. Icon links get aria-labels.
- Settings: quotas load through a shared quotaService (also used by the
dashboard); sections match the side navigation, which now follows
scrolling via a small paperScrollspy directive; copy explains each
option; account card with Sign out; delete moved into a danger zone;
Save shows Saving/Saved and the error alert uses the paper palette.
- Conferences list and detail: sort and status buttons show their state,
hidden statuses appear as chips with a count line, Remove is a button
behind a divider, dates spell the month, expiry column matches the
dashboard, detail page gets an Edit button and plan/cost meta.
- New conference: validation errors only appear after a field is touched
or the form submitted; pricing copy matches how price is computed.
- Status page: progress label no longer overlaps the details below it;
"Report a bug" points at the template and says whom it is for.
- Claim: single rule, constrained width, explains when to use it.
- Anonymize: shorter placeholder, consistent Auto-update label.
- Mock server gains the endpoints these pages need and an ANON mode.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Anonymous GitHub
Share your code and data for double-anonymous peer review — without giving your identity away.
Public instance · How it works · Self-hosting
Why
Double-anonymous review asks you to anonymize the artifact behind your paper — the code and data — exactly like the paper itself. Doing that by hand (owner, organization, repository name, logins, and every mention buried in the files) is tedious and easy to get wrong. Anonymous GitHub does it for you and serves the result behind a shareable link.
A free public instance is available at anonymous.4open.science.
What it anonymizes
- The GitHub owner, organization, and repository name
- File and directory names
- File contents of every extension (Markdown, text, source code, …), replacing a configurable list of terms
Usage
Public instance
Just open anonymous.4open.science, paste your repository URL, add the terms to hide, and share the generated link.
CLI
Anonymize a repository locally and produce an anonymized zip:
npm install -g @tdurieux/anonymous_github
anonymous_github
Self-hosting
Run your own instance with Docker
1. Clone and install
git clone https://github.com/tdurieux/anonymous_github/
cd anonymous_github
npm i
2. Configure GitHub access — create a .env file:
GITHUB_TOKEN=<GITHUB_TOKEN>
CLIENT_ID=<CLIENT_ID>
CLIENT_SECRET=<CLIENT_SECRET>
PORT=5000
DB_USERNAME=
DB_PASSWORD=
AUTH_CALLBACK=http://localhost:5000/github/auth
GITHUB_TOKEN— create one at https://github.com/settings/tokens/new with thereposcope.CLIENT_ID/CLIENT_SECRET— from a new GitHub App at https://github.com/settings/applications/new.- The App's callback must be
https://<host>/github/auth(matchingAUTH_CALLBACK).
3. Start the server
docker-compose up -d
4. Open http://localhost:5000. The port can be changed in docker-compose.yml; putting Anonymous GitHub behind nginx is recommended for HTTPS.
For an optional remote, hidden, delayed MongoDB replica and backup source, see the MongoDB replication guide.
Scope of anonymization
In double-anonymous review, the boundary of anonymization is the paper plus its online appendix — and only that. Googling part of the paper or appendix to reveal authorship is considered a deliberate attempt to break anonymity (explanation).
How it works
Anonymous GitHub either downloads the full repository and anonymizes each file, or proxies requests to GitHub on the fly. In both cases the original and anonymized versions are cached on the server, so even large repositories stay responsive.
Related tools
- gitmask — contribute anonymously to a GitHub repository.
- blind-reviews — browser add-on that hides identifying information when reviewing a pull request.