Skip to main content

Description

This script helps analyze GitHub repositories for a user or organization. It fetches a list of repositories owned by a user or organization and generated a custom report in a number of formats.

In particular, it was designed for showing the size of repositories and the LFS storage they use. Unfortunately the GitHub API doesn't report the LFS usage, so this tool with clone the repos in order to get the LFS size. This is slow, but it is the primary purpose of this tool, since there's no other way to do it.

Requirements

Local Development Setup

  • Create a virtualenv: virtualenv <path>
  • Activate your virtualenv: source <path>/bin/activate (on Linux/Mac), source <path>/Scripts/activate (in bash on Windows), or <path>\Scripts\activate.bat (in Windows command prompt)
  • Use pip install -r requirements.txt in your virtualenv to install required libraries.
  • Run python github_report.py. You may need command-line options to specify options. See python github-storage-usage.py -h for option help.

Authentication

Without authentication you can generate a report for any user's or organization's public repos. To include private repos you will need to authenticate as a user who has permission to see them. To do so, log into GitHub and generate a personal access token that has at least the repo permission. Pass this token on the command-line to the --token option, or put it in a .token file (or some other file that can be read with the --token-file option).

Metadata

Release files for github-report 0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for github-report 0.1
File Size Uploaded Provenance
github-report-0.1.tar.gz 3.1 kB Without provenance Details

Release files / github-report-0.1.tar.gz

Download URL github-report-0.1.tar.gz
Size 3.1 kB
Tags Source
SHA-256 checksum
How to use checksums
0b660e1a33b7045ce5ce30fe4ed4d2bf8a17c8135e4efabb567354e38d1627bf
BLAKE2b-256 checksum
How to use checksums
2b358cb01d380209f44ab1f41ba6e57b533da522bb64ca668bc8c608269d629f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.3.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.7.3

Security for github-report 0.1

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.

Release history Release notifications | RSS feed

This release

0.1 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page