Maybe I'm missing something really obvious, but... 3,800 repos? I guess I find it kind of surprising they have that many!

▲

PAndreew 4 hours ago | parent | next [-]

As others have said it's just a fraction. I'm in a medium size tech-related company and we have 7500+ in one Github org. We have two orgs, so altogether easily 10K+. Of course most of it is stale, obsolete, sandbox, personal tools, etc. I wouldn't be surprised if Github would have 100K+ internal repos or even more.

▲

htrp 3 hours ago | parent [-]

no pruning of repos?

▲

sbarre 3 hours ago | parent | next [-]

No OP but I used to work at a large company with a similar number of repos.

When I left about a year ago, we had just started (after being on Github for almost 8 years) an ongoing project of first archiving old/outdated repos in place, and then moving them to an "archived" sub-org, and waiting to see if anyone complained.

Previously no one wanted to outright delete or remove repos because of the risk that someone somewhere was relying on it, and also there was no actual downside to just leaving them there (no cost savings, no imminent danger other than clutter, etc), so resources were never allocated to do it. There was always something more important to work on.

In an org with a higher floor of engineering management, a proactive program for removing unused or outdated repos would absolutely be expected though I think.

	▲	a_t48 an hour ago \| parent [-]
		This is a continual fight for me. At nearly every company I've had to compromise on using a graveyard repo for packages within a monorepo, even though git has the whole history already.

▲

NewJazz 2 hours ago | parent | prev | next [-]

Gitlab is so nice for this. You can group repos together so it is harder to lose track of stale projects.

▲

fn-mote 2 hours ago | parent | prev [-]

Breaks old stuff

▲

ashishb 4 hours ago | parent | prev | next [-]

Uber had 8000 repos at one point with 2000 engineers - https://highscalability.com/lessons-learned-from-scaling-ube...

	▲	Gigachad 44 minutes ago \| parent [-]
		Probably most of them are forks of some public repo with some patch applied and half of those are probably not even used internally anymore.

▲

philipp-gayret 4 hours ago | parent | prev | next [-]

I worked for a food retail store once. I remember going in the first day wondering, how hard can it really be... From the outside, it looks like they have a simple website. The website to order things on was an amalgamation of 300+ repo's. GitHub lost less in this breach. It takes a lot of effort to keep things simple as you grow.

	▲	robotnikman 2 hours ago \| parent [-]
		Can confirm as someone working in the same field, we have a ton of repos

▲

ryanhecht 2 hours ago | parent | prev | next [-]

Something cool that I've always liked about working at GitHub is how much of the company _runs on GitHub_ -- A lot of teams, even non-technical teams, have their own repos just to organize docs/SOP's/designs/etc like a traditional knowledge work company might use a Sharepoint

▲

tempay 4 hours ago | parent | prev | next [-]

Personally I have over a hundred, especially from quick prototypes, studies or instances of templates so I can easily see how over 18 years and many hundreds of employees you end up with thousands.

▲

MrDarcy 4 hours ago | parent | prev | next [-]

3800 is low for an org like GitHub. Glad it’s highly likely not all their repos are compromised.

	▲	organsnyder 4 hours ago \| parent [-]
		Given the attack vector, it's possible that the impacted repos were ones that see more activity.

▲

dgellow 4 hours ago | parent | prev | next [-]

I was part of an org with more than 15k repos

▲

newsoftheday 4 hours ago | parent | prev | next [-]

It sounds low to me, I worked at a Fortune high number a few years ago and they had more.

▲

skissane 3 hours ago | parent | prev | next [-]

In my personal experience, give it a decade or two, and any corporation will accumulate hundreds (or even thousands) of abandoned internal repos containing discontinued services, POCs/prototypes that never went anywhere, etc – people forget to archive them, or aren't sure whether something is still in use or not so err on the safe side.

AI is making this even worse. With coding agents, anyone can throw together a quick internal prototype of any idea they have, even if it has no hope of ever making it to production.

▲

unix4ever 3 hours ago | parent [-]

Maybe though AI will make it better, assign agents to monitor, maintain and keep repos up to date or via A2A refer them to an agent to dispose of them in accordance with company requirements. I actually think AI will greatly help this type of problem.

	▲	skissane 2 hours ago \| parent [-]
		Autoarchiving repos which nobody has used in X years doesn’t require any AI - you can just write a bot to do it. People don’t, because it isn’t a priority. AI can make writing such a bot a bit easier, but can’t help much with getting approval from the powers that be to run it.

▲

4 hours ago | parent | prev | next [-]

[deleted]

▲

noelsusman 4 hours ago | parent | prev | next [-]

Am I missing the joke here... they have hundreds of millions of repos.

	▲	dijit 4 hours ago \| parent \| next [-]
		I think they mean that these are internal github-org repos. The ones used for running the site itself. Though, its so many that i think there are some customer ones in there too.
	▲	nightpool 4 hours ago \| parent \| prev \| next [-]
		No, there's no joke, you might have just misread the article (the 3,800 number is the number of internal GitHub repos the employee had downloaded on their personal computer / had access to on their own GitHub account)
	▲	Galanwe 4 hours ago \| parent \| prev [-]
		The breach is about internal repositories, not user repositories.

▲

eddythompson80 4 hours ago | parent | prev | next [-]

really? I mean these are internal repos. Probably most of them are random one-off experiments or a place to park code. Google has 2,900 "public" repos on github. Microsoft has ~8k "public" on github too. Can't even imagine how many they have on their internal systems.

▲

paulddraper 4 hours ago | parent | prev [-]

They have 800 engineers. So 3,800 repos is high, but not crazy.

Some of those could be forks.