Ask HN: Why did the number of new GitHub repos crash in late 2022? | Hacker News Reader

Ask HN: Why did the number of new GitHub repos crash in late 2022?

11 pointsArnehuang7 comments

I was looking at the data from https://ossinsight.io/explore/?id=6c060cc1-83b4-43f7-be4a-a401e4a5387f. I filtered to US only but across the board there was a large crash around August 2022. Curious if anyone knows why.

View on HN

When you see stuff like this happens. It’s most likely something wrong with the tool that is gathering this data. They lost data access or something funky like the max number of pages they can iterate went down

On clickhouse I can't see that crash. IIRC clickhouse sources their data from https://www.gharchive.org/

The query I used: https://play.clickhouse.com/play?user=play#U0VMRUNUIAogICAgZ...

EDIT: just saw that ossinsight also uses gharchive

I didn't filter for US region though. This is not really published by the github api, only the "location" field is published where users can put everything. ossinsight probably tried to parse the country codes?

But on ossinsight only ~5% of the users have a country code attached to https://ossinsight.io/explore/?id=28da49bd-fec9-4720-a4df-da...

People not wanting copilot to be trained on their code?

Could it be due to [0]:

> Most likely better bot protection, almost all of npm is currently scrapped to teach ai bots coding

[0]: https://old.reddit.com/r/programming/comments/16mna5z/whats_...

Mandatory 2FA announced mid 2022?

I'd probably put money on that. Not that it stopped people from creating repos but that it did something with the permissions of the tool gathering the data and the rate limiting to reduce the amount of data ingested.

that query isn’t for new Github repos, it’s for the number of github repos the counter was 1. allowed to count and 2. knew how to count. all that said it is pretty interesting 90k repos went away somehow between August 1 and September 1 last year. Good question. (Also, interesting tool. Never heard of ossinsight before.)

Reply on news.ycombinator.com