19 points kernelrocks 1 hour ago 5 comments
dorianmariecom 1 hour ago | parent
same on github or gitlab etc
poly2it 55 minutes ago | parent
They compare this in the article:
Platform | Repos scanned | Verified-live credentials | Per 1K repos
----------+---------------+---------------------------+-------------
Bitbucket | ~2,600,000 | 6,212 | 2.39
GitLab | ~5,600,000 | 17,430 | 3.11
Gitee | 7,256,531 | 26,400 | 3.64LoganDark 22 minutes ago | parent
I wonder if this is because of providers scanning those platforms more than they scan Gitee, or the platforms themselves notifying the providers. Fairly sure that GitHub, for example, supports spotting certain live credentials on push and immediately notifying the platform to revoke it. And plenty of providers also watch the open web for live tokens and revoke them immediately.
owlninja 17 minutes ago | parent
From the article
> It has no public equivalent of the platform-vendor secret-scanning partnerships that have become standard on GitHub.
nitroedge 34 minutes ago | parent
So what happens if someone uses some of these credentials and enjoys free AI for as long as they are active? Just curious if this is is criminally enforced now and what the penalties have been?
I remember there was a site awhile ago that listed Ollama instances which were made open to the public and had the # of tokens/sec throughput beside each one.