Skip to content

Repository collaboration

Put your real-world private repo to work.

We work with substantial, real-world codebases to build and test developer tooling. If you maintain one, there's a collaboration here — on access you scope yourself and revoke whenever you like.

Apply to collaborate How it works

● Opt-in only. We don't cold-email — you come to us.

The bar

What qualifies a repository

These are hard thresholds. Clear all four and it's a strong fit — a single repository is enough, it doesn't have to be a whole portfolio.

100k+

Lines of code

Genuine source — not generated or vendored files.

500+

Commits

A real development history, built up over time.

100+

Pull requests

Reviewed, merged, collaborative work.

1

Private & active

A real project you still maintain.

Check it yourself

You run the script. We never touch your code to do it.

The evaluation is a small open script you run on your own machine. It counts commits, pull requests, lines, and structure, and prints a summary. That summary is all you send us. Read it before you run it — the source is right there.

github.com/codercops/repo_meta_data_script ↗
run the evaluation
$ git clone https://github.com/codercops/repo_meta_data_script
$ cd repo_meta_data_script
$ pip install -r requirements.txt
$ python repo_analyzer.py --path /your/repo
# → prints a metadata summary you can share

The process

How the collaboration works

Four steps, and you hold the controls at every one. No access to your code changes hands until you decide it does.

  1. Run the evaluation script yourself

    Clone our open script and run it against your own repository. It reads metadata only — commit counts, PR counts, lines, structure. Nothing is sent to us, and you see exactly what it does before you run it.

  2. Share the result

    Send us the summary the script produces. That's how we check the repo against the criteria. Still no access to your code at this stage — just the numbers.

  3. We confirm the fit and next steps

    If the repository qualifies, we get in touch to talk through how the collaboration works and answer anything you want to ask first.

  4. You grant scoped, read-only access

    If you decide to go ahead, you issue an access key limited to just the repositories you chose — read-only, nothing else. You can revoke it at any time.

On access & trust

What we access, and what we never will

Your code is your business, often literally. The collaboration is built so you never have to over-share to take part.

What we access

  • Commit and pull-request counts — the qualification metrics.
  • Language and framework breakdown, for fit.
  • Only the repositories you explicitly select.
  • Read-only access you can revoke whenever you want.

What we never do

  • Ask for your personal account token.
  • Request write, admin, or org-owner access.
  • Touch a repository you didn't choose.
  • Need your secrets, keys, or environment files.

One ask in return: only offer a repo you have the right to share.

Apply

Think your repo clears the bar?

Run the script, then send us the summary with a line about the project. If it's a fit, we'll take it from there.

Email your application →

averma@codercops.com · we reply to every application