# bigcode-fetcher
A utility to search and fetch code from GitHub. This tool was build to easily create datasets for repository analysis.
The tool works in two phases, search finds repositories using the GitHub API, and saves the result in a JSON file. download fetch all the repositories inside the JSON file.
## Install
This tool can be installed by running
` pip install bigcode-fetcher `
or by fetching this repository and running
` pip install . `
in this directory.
## Usage
### search command
By default, the utility searches for repositories fulfilling the following conditions
size between 1M and 100M
stars count > 10
non-viral license (MIT,Apache-2.0,MPL-2.0,BSD-2-Clause,BSD-3-Clause,BSD-4-Clause,MS-PL)
and retrieves the first 100 projects, ordered by number of stars.
To avoid API rate limiting, an access token can be provided either with the –token CLI argument or with the GITHUB_TOKEN environment variable.
See the help to see all the options:
` bigcode-fetcher search -h `
#### Example
Search for all Apache commons projects written in Java
` mkdir -p apache-common-projects bigcode-fetcher search --language Java --user apache --stars '>0' --keyword commons --max-repos 500 -o apache-common-projects/apache-commons.json `
### download command
This commands will simply git clone all the repositories in the JSON generated by the search command.
To reduce the download size, only the latest revision is fetched by default (i.e. git clone –depth 1). This can be disabled by passing in the –full flag.
USERNAME/REPO will be fetched in OUTPUT_DIR/USERNAME/REPO, where OUTPUT_DIR is set by the –output option.
The command will ignore the project if the directory already exists, so running the command multiple times is safe, and recommended to make sure all repositories have been fetched.
See the help for more information:
` bigcode-fetcher download -h `
#### Example
Download all the Apache commons project generated above
` mkdir -p apache-common-projects/repositories bigcode-fetcher download -i apache-common-projects/apache-commons.json -o apache-common-projects/repositories `
Metadata
Release files for bigcode-fetcher 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| bigcode-fetcher-0.1.2.tar.gz | 5.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bigcode_fetcher-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.1 kB
Release files / bigcode-fetcher-0.1.2.tar.gz
| Download URL | bigcode-fetcher-0.1.2.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c24fd921cc86d3b327ad9ab99faa10eafd40b948368d76f3abff9a40dbf1524
|
|
BLAKE2b-256 checksum How to use checksums |
97ba16e36d081a5c03ce21e411a98999375c5eb959d92d6e7405838fbcf9cd76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / bigcode_fetcher-0.1.2-py3-none-any.whl
| Download URL | bigcode_fetcher-0.1.2-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
97d929d59d68a39fd59dbd37acd2163357eb3343af2dd19c64ad5ec01cc900ad
|
|
BLAKE2b-256 checksum How to use checksums |
c3ffb7e4d79f7eb0c02cb1675e3173d109d447ff36f8b2298cd5f50f837d50f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bigcode-fetcher 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.