• Blog
  • Introducing The GitHub CloudQuery Provider

Introducing The GitHub CloudQuery Provider

Ron Eliahu
Ron Eliahu

CloudQuery is an open-source, extendable framework that gives you a single-pane-of-glass to your cloud-infrastructure using SQL. Today, we are happy to announce the release of the GitHub Provider for CloudQuery.

GitHub is a source-control provider that helps developers store and manage their code, as well as track and control changes to their code.

In this tutorial, we will install CloudQuery and use it to fetch GitHub resources. Then, we will use SQL to get visibility into security, compliance and cost-management in GitHub.


First we need to download the pre-compiled CloudQuery binary. We can also install it with the following brew command:

brew install cloudquery/tap/cloudquery
# After initial install you can upgrade the version via:
brew upgrade cloudquery

Before running CloudQuery we need to generate a config.yaml via the init command:

cloudquery init github

Now that we have our config.yaml ready we need to add our GitHub Personal Access Token. The required scopes:

  • read:org
  • read:project
  • public_repo

To create one, refer to this guide by GitHub. This token should be considered a secret and the config file should not be committed to source control.

Add the token we created, and the organization(s) you want to fetch, to the configuration.

  - name: github
      access_token: "<YOUR ACCESS TOKEN HERE>"
      orgs: ["<YOUR ORG NAME>"]
      - organizations
      - repositories
      - teams
      - billing.actions
      - billing.packages
      - billing.storage
      - issues
      - hooks
      - installations
      - external_groups


CloudQuery requires us to connect to a database. Either use an existing one (we change the dsn in the config.yaml), or simply create a database with the following command

docker run -p 5432:5432 -e POSTGRES_PASSWORD=pass -d postgres

Finally, we can execute CloudQuery to fetch all our GitHub resources. Simply run the fetch command and let the magic happen.

cloudquery fetch

Use Cases

After we finish fetching our config data we can make queries for security, compliance, cost management and other purposes.

Find all Public Repositories

-- Query all repositories in the organizations that are public
SELECT id, org, name, description, created_at_time, pushed_at_time,
updated_at_time FROM github_repositories
WHERE private = false

List All Organization Owners

-- Find all users in organization that have the admin role
SELECT id, org, login, role, state FROM github_organization_members AS gom
    INNER JOIN github_organization_member_membership gomm ON gom.cq_id = gomm.organization_member_cq_id
WHERE role = 'admin'

Organization Billing

-- Get billing information state for actions, packages and storage
SELECT * FROM github_action_billing
SELECT * FROM github_package_billing
SELECT * FROM github_storage_billing

Long Standing Open Issues

-- Find all open issues that have been open for more than 7 days
SELECT gr.org, gr.name, gi.id, gi.state, gi.user_login AS opened_by, gi.created_at, gi.updated_at
FROM github_issues gi
INNER JOIN github_repositories gr ON gr.id = gi.repository_id
WHERE state = 'open' AND NOW() - interval '7 days' > created_at

What's next

We are going to continue expanding the GitHub Provider, adding support for more resources. Interested in seeing another provider? Check out Developing New Provider and/or open an issue on our GitHub.