6 ms·
Claim: Private GitHub repos included in AI dataset
- pluc 3y agoCould "private" mean "kept from the outside world"?
- latexr 3y agoFull text from the post: > If you had code on GitHub at any point it looks like it might be included in a large dataset called “The Stack” — If you want your code removed from this massive “ai” training data go here: > https://huggingface.co/spaces/bigcode/in-the-stack https://huggingface.co/spaces/bigcode/in-the-stack > I found two of my old Github repos in there. Both were deleted last year and both were private. This is a serious breach of trust by Github and @huggingface. > Remove all your code from Github. > CONSENT IS NOT OPT-OUT.
- samtheprogram 3y agoThought it was bait, but I can confirm I can find private repos in the search results. What the heck?
- tailspin2019 3y agoWere those repos always private?
- simonw 3y agoWhich private repos? Any that you're willing to share (I get that sharing names of private repos goes against the whole idea of them being private!)
- rfoo 3y agoSince your repo's name is public now anyway, could you please help us and post it here? I'm really curious about what happened. Since public GitHub activities were archived [1], if you post it here we can check if it were ever public or it's truly private at all time. [1] https://www.gharchive.org/ https://www.gharchive.org/
- johncoatesdev 3y agoHow do I check this? I found a repo I'm pretty sure was always private on there that I deleted a while back. https://github.com/johncoates/JCBootstrap https://github.com/johncoates/JCBootstrap There's no archived version on archive.org at least.
- simonw 3y agohttps://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://github.com/johncoates/JCBootstrap https://archive.softwareheritage.org/browse/origin/directory... shows a "snapshot date" of "11 August 2015, 07:28:00 UTC" - any chance it was public on that date such that the crawler could have accessed it?
- sdesol 3y agoI checked my GitHub archive (https://www.gharchive.org/ https://www.gharchive.org/) indexed data and the only repo that I saw for johncoates was LanscapeVideos, which has a last event time of 2015-06-09 07:09:52+02 It is important to note that GitHub archive is not 100% accurate and there is over 319 missing hours.
- johncoatesdev 3y agoI can't find any reason why I would have made it public. I made the repo in 2014 for internal use and don't like to share projects like that. I'm pretty careful when releasing any code publicly. It's some code that other private projects depend on. I searched for any references in public code and there are none, so there should have been no reason to make it public. Interestingly my public code with thousands of stars isn't in "The Stack".
- bredren 3y agoThis shouldn't be something where we're relying on recollection. Presumably github repo privacy state has an audit trail. This would allow GH to prove / disprove claims on any given repo easily. I hope a rep steps in to do so.
- tailspin2019 3y ago> "Both were deleted last year and both were private" I'd really like to know if they were ever public at any point because that might explain it. None of my repos that have always been private are included (apparently). That's not to say I'm not concerned by this...
- kevincrane 3y agogod the language in that opt-out link is patronizing as hell. do AI people just assume everyone is happy to be a cog in their monetization scheme?
- CatWChainsaw 3y agoThey assume that they don't need to care and their assumption has so far proven correct.
- codazoda 3y agoThis is interesting... I have 66 repositories picked up and put in The Stack. I spot-checked the first 10. All 10 are Public on GitHub. 8 of the 10 do not have a license of any type, meaning they are covered by copyright, at least in the US, unless GitHub has some terms extending the license of public projects to 3rd parties. One of mine is Private and was an extension I sold for a short time. I can't say if I ever made it public or not. https://github.com/codazoda/like_roller https://github.com/codazoda/like_roller
- tailspin2019 3y agoFrom one of the comments on that post: > I work for github. This post was shared in our slack, on a non work related channel. We don't think it's us. > They say they get data from SoftwareHeritage, a website that archives repos from github. If your repos were ever open, they might have been archived there even after you deleted from github. > That's my best guess.
- latexr 3y agoThe OP responded to that: https://hachyderm.io/@emenel@post.lurk.org/112128613137436381 https://hachyderm.io/@emenel@post.lurk.org/11212861313743638... > thanks for the additional info. I’m pretty sure the repos of mine were private. If it were only me i could be misremembering something, but i have heard from a number of people that they also found repos in this dataset that were private. So i’m not sure what to think or how to explain it.
- deleted 3y ago[deleted]
- simonw 3y agoThis is talking about The Stack. The poster says: "I found two of my old Github repos in there. Both were deleted last year and both were private." The Stack was constructed a while ago, so "deleted last year" wouldn't have an impact if it was constructed before then. "Both were private" is the thing that needs to be unpacked here. Were these genuinely private repositories that had never been made public on GitHub? https://huggingface.co/datasets/bigcode/the-stack-v2 https://huggingface.co/datasets/bigcode/the-stack-v2 talks about where the Stack comes from: "This dataset is derived from the Software Heritage archive, the largest public archive of software source code and accompanying development history" You can search that here: https://archive.softwareheritage.org/browse/search/?q=simonw%2F&with_visit=true&with_content=true https://archive.softwareheritage.org/browse/search/?q=simonw... - it would be interesting to know if the OP's "private" repos are included in that collection.
- errantmind 3y agoFor info, I checked and it looks like none of my AGPL licensed repos are included in The Stack. Neither are my private repos.
- tom_ 3y agoMy GPL ones seems to be excluded. I've got a couple that are intended to be GPL, but you wouldn't know unless you go to the GitHub issues to find the issue I raised about the licence file not being in the repo. They are included.
- RyanShook 3y ago[flagged]
- sdflhasjd 3y agoHmm, I do see some of my repos there, but only public ones. It would seem a bit too foolish of GitHub to put private repositories in a public dataset. Is there any other corroboration or proof?
- jaggederest 3y agoIt would be fun to upload a private repo with AWS keys in it as a canary. If the account ever gets used, the repo is no longer private?
- rvz 3y ago[flagged]
- ametrau 3y agoWas there a previous time?
- cabirum 3y ago[flagged]
- ergonaught 3y agoAs with others, I can say they only seem to have my repos that were ever public. Nothing of mine that was always private is showing.
- roland35 3y agoIt is always interesting to see how copilot autocompletes things like "Todo: " or "my ssh key" and see what data leaks through!
- throwitaway222 3y agoI mean, there is also a lot of "public" github repos that contain absolutely copywritten work too.
- nromiun 3y agoI also see a 7 years old private repo from my account. But I may have made it public initially, I don't really remember it. Anyone knows how to check if a repo was ever made public?
- rfoo 3y agoCheck if it was ever appeared in gharchive [1]. [1] https://www.gharchive.org/ https://www.gharchive.org/
- netule 3y agoThe Wayback Machine [0] if you're lucky (?) enough to have had it indexed. [0]: https://web.archive.org/ https://web.archive.org/
- abdullahkhalids 3y agoIf the repo was public for a while (say 2 years), and then became private, then the code in the Stack for your repo must be 5 years old. If on the other hand, it's tracked to the latest commit, that is a different scenario.
- nyc_data_geek 3y agoI am Jack's complete lack of surprise. In all seriousness, without strong data privacy regulations (ie: GDPR), we will continue to see this sort of stuff, as the potential monetary rewards for using this sort of data far outweigh the potential liability. Cost of doing business type stuff, rather than an existential risk for abusing public trust. My opinion is that data should be treated like a fissile element - very dangerous to hold and store, but extremely powerful when properly employed. However, it's only dangerous if the liability of storing it is significant and real, as of today, it's not (in the US).
- psuedo_uuh 3y agoIt blows my mind that we’re all fine with “the home of open source software” is closed source
- bogwog 3y agoThe way I rationalize my use of Github to myself is by framing it as me stealing free compute and storage from the evil Microsoft.
- HaZeust 3y agoTrust me, they're making it back.
- mdaniel 3y agoI'd presume if nothing else in copilot subscriptions, populated by harvesting upteen bazillion repos, issues, and maybe even CI job run logs
- mnau 3y agoi am pretty sure they would just clone stuff from BitBucket or SF if they didn't have it on their own platform.
- mdswanson 3y agohttps://aibusiness.com/nlp/github-copilot-loses-20-a-month-per-user https://aibusiness.com/nlp/github-copilot-loses-20-a-month-p...
- simonw 3y agoThe accuracy of that story was vigorously denied by people in a position to know: https://twitter.com/natfriedman/status/1712140497127342404 https://twitter.com/natfriedman/status/1712140497127342404
- mdaniel 3y ago
- jmuguy 3y agoNeed more proof than "pretty sure they were private" and "heard from a number of people".
- pityJuke 3y agoThis organization claims that they'll allow you to opt-out, but they haven't seemingly done so for the oldest request on their repository [0]. Pathetic. [0]: https://github.com/bigcode-project/opt-out-v2/issues/1 https://github.com/bigcode-project/opt-out-v2/issues/1
- misterpigs 3y agoThis is a nothingburger. I have "private" repos listed in the dataset but they were all at one time public. Searching the SoftwareHeritage site I can find those once-public repos with ancient commits. My private repos that were always private are not listed in the dataset.
- Retr0id 3y ago47 of my repos are in the stack, and none of them are private (and I have plenty of private repos)
- multimoon 3y agoSame here. I think some people are confusing private now vs private since creation.
- Retr0id 3y agoI do think, however, that "repo no longer public" should be treated as an opt-out signal.
- Mtinie 3y agoWhich is valid, but what's the timeframe for rechecking and validating if there's been a change? I'll posit it's practically impossible to catch every single change within a reasonable timeframe to ensure that "a repo no longer public, today, within a data set collected earlier" would be excluded. I may be misunderstanding your suggestion. If so, I'm curious to learn what I missed.
- Retr0id 3y agoMy assumption is that the "my private repo was included" crowd are misremembering that their repo used to be public at some point in the distant past (~years). My suggestion would be that they re-scan before each major revision of the dataset (such as this upcoming "v2" release). This would be a relatively expensive process given the numbers involved, but so be it. (edit: I think "v2" is already released, but you get my point)
- Mtinie 3y agoI can get behind this idea. Thank you for clarifying.
- inopinatus 3y ago
- caesil 3y agoAll of the comments here where the commenter found their repos say either "it only has the public ones" or "it has some private ones from x years ago and i don't quite remember if they were ever public". So it seems probable this is a case of repo owners misremembering.
- jtietema 3y agoI agree. Only my public repos are in the data set.
- angst_ridden 3y agoI'm curious how they get around licenses. For example, I have repos that show up in The Stack. Some have licenses that require inclusion of the copyright in any source re-use or redistribution. IANAL, but it seems like inclusion in the data set and subsequent distribution without the copyright notice would be a violation.
- xyst 3y agoProbably some obscure GH legal clause stating “we own your data. Ownership is implied and we may do anything with it. Private vs public is a concept of accessibility over the internet. Not necessarily means it’s not accessible via intranet or other non-public means” It’s the similar legal clauses used for decades on social and video hosting platforms.
- angst_ridden 3y agoI don't think that gets around the code licenses. They may use it as if it does, but I'm not convinced that would hold up if soemone were wealthy enough to make a court case.
- ADeerAppeared 3y agoGH interestingly doesn't grant themselves nor others that many rights. --- You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program. --- Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). --- They don't even include training for copilot (though a dodgy lawyer will likely try to include that as "part of providing the service). 3rd parties only get a license to fork your repo, seemingly not even a license to do anything with that repo. (And hot take: Github should just let people disable the fork button already.)
- xyst 3y agoThe crypto craze stole our energy to validate digital currency transactions on the blockchain. Now the AI craze stole our code and collective knowledge to ultimately train their models, and hopefully replace SWEs and other knowledge based fields (ie, medicine). At least with blockchain, some people got rich. But with the AI craze the only people getting rich are the rich themselves.
- latexr 3y ago> At least with blockchain, some people got rich. But plenty more lost money or went bankrupt. The one’s who got rich did so at the expense of other non-rich people.
- remotefonts 3y ago> But plenty more lost money or went bankrupt. The one’s who got rich did so at the expense of other non-rich people. [citation needed]
- codr7 3y agoLogical reasoning is still a valuable tool. Where else would the money have come from?
- remotefonts 3y agoI got "rich" also, but I've never speculated, and TBH I've sold, and spent, more spent than sold at all kind of valuations, and most of the riches are still unrealized, so, sorry if I doubt what you say.
- a_wild_dandan 3y agohttps://en.wikipedia.org/wiki/Cryptocurrency_and_crime#notable_thefts https://en.wikipedia.org/wiki/Cryptocurrency_and_crime#notab... https://en.wikipedia.org/wiki/Bankruptcy_of_FTX https://en.wikipedia.org/wiki/Bankruptcy_of_FTX https://en.wikipedia.org/wiki/OneCoin https://en.wikipedia.org/wiki/OneCoin https://en.wikipedia.org/wiki/Bitconnect https://en.wikipedia.org/wiki/Bitconnect Etc.
- deleted 3y ago[deleted]
- simonw 3y agoSince a lot of this depends on whether someone had ever had a private repo public in the past, I was hoping it could be resolved using the GitHub security audit log. You can access that for your repos here: https://github.com/settings/security-log https://github.com/settings/security-log Then search for repo:simonw/datasette or similar. But... it looks like the audit log only goes back 6 months, so sadly it's not useful for reviewing this particular situation which involves repos that could have been 5 or more years old. The ClickHouse copy of the GitHub Archive is useful for reviewing things and goes back a lot further. Try it here: https://play.clickhouse.com/play?user=play https://play.clickhouse.com/play?user=play You can run this query to see relevant events for a specific username: with public_events as ( select created_at as timestamp, 'Private repo made public' as action, repo_name from github_events where actor_login = 'simonw' and event_type in ('PublicEvent') ), most_recent_public_push as ( select max(created_at) as timestamp, 'Most recent public push' as action, repo_name from github_events where event_type = 'PushEvent' and actor_login = 'simonw' group by repo_name ), combined as ( select * from public_events union all select * from most_recent_public_push ) select * from combined order by timestamp The PublicEvent one is "When a private repository is made public" according to https://docs.github.com/en/rest/using-the-rest-api/github-event-types?apiVersion=2022-11-28#publicevent https://docs.github.com/en/rest/using-the-rest-api/github-ev... I just built a tool for running this query without having to type in the SQL: https://observablehq.com/@simonw/github-public-repo-history https://observablehq.com/@simonw/github-public-repo-history Explained in this TIL: https://til.simonwillison.net/clickhouse/github-public-history https://til.simonwillison.net/clickhouse/github-public-histo...
- dangnetgod 3y ago[flagged]
- buffington 3y agoNot all of us do, bro.
- deleted 3y ago[deleted]
- drpossum 3y agoI'm guessing these were public once (mine were), but I'll be damned if I let github host anything of mine again.
- latexr 3y agohttps://archive.is/nWzk4 https://archive.is/nWzk4
- mtam 3y agoJust to add yet another data point. Only my Public repos included. All my private repos are not included.
- falsandtru 3y agoIs there any other good service for enterprise development?
- zzo38computer 3y agoI do not use private GitHub repositories. (If I want something private, I will store it on my own computer and/or on DVDs, etc.) If they are using private data in AI dataset (or other uses) then that is a serious issue; they are copying data which is meant to be private. (Public files are public and should be made copies that others can use too, though.)
- t1c 3y agoEven though they were only my public repos in there, I really don't like this being opt out instead of opt in, especially since some of those repositories were not under fully permissive licenses
- AshamedCaptain 3y agoSo let me understand this. Step 1) "Software Heritage" crawls the web (not only Github; they definitely crawl ANY gitlab instances they find online among practically everything else). They "store" ANY type of source code, irregardless of the license of that code. They admit as much in their own FAQ ( https://www.softwareheritage.org/faq/#24_What_is_the_policy_for_determining_what_deserves_to_be_archived_are_there_requirements_for_a_GitHub_Gitlab_or_XXX_repository_to_be_archived_by_SWH https://www.softwareheritage.org/faq/#24_What_is_the_policy_... ) : > Software Heritage archives everything that is publicly available, without preliminary tests or checks [for LICENSE file or others]. You are responsible for checking whether the source code you find in the archive can be reused, and under which terms. Step 2) "Hugging Face" uses the Software Heritage dataset to build some AI training dataset ("The Stack"), again, completely ignoring licensing. You apparently have to manually opt-out if you don't want your COPYRIGHTED source code to be included there. But as far as I can see, opting out is only considered AT ALL for Github repositories via https://huggingface.co/datasets/bigcode/the-stack-v2 https://huggingface.co/datasets/bigcode/the-stack-v2 . If you have your source code published outside Github, then your code appears to be used, period. > The Stack v2 is a collection of source code from repositories with various licenses. Any use of all or part of the code gathered in The Stack v2 must abide by the terms of the original licenses [...] Step 3) Eventually and inevitably someone releases some model trained on this dataset, ignoring licensing again. Step 4) Someone uses code generated from such chatbot, unknowingly violating everything software license known to man. Step 5) ??? Step 6) Profit! Where do these "Software Heritage" guys mention which user-agent their crawler is using so that I can permanently ban them from my websites? At least archive.org does that and they have a much nicer way to request exclusion from their archive.
- a_wild_dandan 3y agoYou lost me at step four. If reading source is fair use and generating content isn't derivative work, this is kosher. As litigation mounts, we'll learn more. To me, a learning path that's acceptable for humans is acceptable for AIs. All of the rationales for treating AI/human learning distinctly feel flimsy and arbitrary. "The difference is learning scale." So what? "LLMs just parrot derivatives of their training data." No, they don't. That's demonstrably false, and theoretically absurd, for all the common cited reasons. "AIs obviously aren't people. So their learning restrictions must be different." Why? "People are financially benefiting from the AI's knowledge!" Yep, that's generally how employment works. Etc, etc. My take could be totally wrong. I get that. It'll be interesting to see where the courts fall on the issue. But personally, the critics' arguments feel profoundly crummy and counterproductive; applying their logic to pre-LLM systems usually results in horrendous alternative realities. But that's just, like, my opinion, man.
- matt3210 3y agoI and most of my coworkers have all found at least one private repo which we believe was always private to be in the data set version 2.
- matt3210 3y agoOpt-out consent is the equivalent of assuming a partner consents because they haven't said anything. Consent is not Opt-out == Yes means Yes
- max_ 3y agoTime for an end to end encrypted Git Service.
- LightFog 3y agoTime to start large scale poisoning of repos.
- tamimio 3y agoEncrypt your private repos..