On a serious note, I'm a bit surprised that GitHub makes it trivial to compute the rate at which new repositories are created. Isn't that kind of information usually a corporate secret?
(I understand many companies default to not expose any information unless forced otherwise.)
Also, having a sequence implies at least a global lock on that sequence during repo creation. Repo creation could otherwise be a scoped lock. OTOH, it's not necessarily handled that way --- they could hand out ranges of sequences to different servers/regions and the repo id may not be actually sequential.
People do this. GitHub started doing it too so now you get a nice email from them first instead of another kind of surprise.
https://docs.github.com/en/code-security/secret-scanning/sec...
and the list is way bigger than I recalled: https://docs.github.com/en/code-security/secret-scanning/int...
>quite a few providers they actually have an integration to revoke them if found in a public repo, which I think is way more handy
Yes I've also gotten an email from Amazon saying they revoked a key someone inadvertently leaked (but so long ago I only remember that it happened). I read my AWS emails at least.
Yes: https://docs.github.com/en/rest/repos/repos?apiVersion=2022-... (you can filter to only show repositories created since a given date).
they have some secret leaking infra for enterprise
Which is arguably even more interesting…