Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GPL code included despite what the documentation claims

Open
#65 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
huggingface, python

Research direction

Start with the “Other known limitations” and “Licensing information” sections linked in the issue, then reproduce the GPL search in StarCoder2 Search and inspect the Software Heritage example. Done means the reported GPL inclusion is reviewed and the dataset or its licensing documentation reflects the project’s decision.

Written by the indexing model from the issue text.

Description

question

In other known limitations, we can read:

To the best of our knowledge, all files contained in the dataset are licensed with one of the permissive licenses (see list in Licensing information) or no license. The accuracy of license attribution is limited by the accuracy of GHArchive and ScanCode Toolkit. Any mistakes should be reported to BigCode Project for review and follow-up as needed.

A search for “under the terms of the GNU General Public License” on StarCoder2 Search returns many entry.

My own GPL code is included, see swh:1:cnt:80ff01eaf4187cf470084f4b0b1fec223691549a as an example. I found this file by searching “diffoscope” in the search engine mentioned above. There is no point in listing a GitHub user, as the code has been embedded in a repository that is not under my control.

Please either state that you include code under the GPL (and other non-permissive licenses) or stop including such code in the dataset.

Dominant language
No language data
Stars
18
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bigcode-project/opt-out-v2

All issues in bigcode-project/opt-out-v2

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.