Skip to main content
Connect your GitHub organization to Draftt to track the dependencies in your repositories. Draftt brings each repository into the Code catalog and flags dependencies that are end of life, deprecated, or no longer maintained. Draftt connects through the Draftt.io GitHub App with read-only access.

​
Prerequisites

  • Owner access to the GitHub organization you want to connect
  • Admin role in the Draftt dashboard (Integrations > GitHub)

​
Setup

1

Open the GitHub integration

In Draftt, go to Integrations and click the GitHub card. If your organization already has a GitHub integration, click Add on the GitHub page. Draftt opens GitHub so you can install the Draftt.io GitHub App.
2

Choose your organization

Sign in to GitHub if prompted, then select the organization you want to connect. Select the organization, not your personal account, to include its repositories.
If your organization uses SAML single sign-on and doesn’t appear in the list, sign in to the organization through your identity provider, then reload the page.
3

Select repository access

Choose which repositories Draftt can read:
  • All repositories includes every current and future repository in the organization.
  • Only select repositories limits access to the repositories you choose.
Draftt scans only the repositories selected for the installation. Repositories you don’t select aren’t scanned, including public repositories.
4

Review permissions and install

Review the requested read-only permissions and click Install.
If you aren’t an organization owner, GitHub may show Request or Install & request instead. GitHub emails your organization owners. The integration connects after an owner approves the request.
5

Return to Draftt

After installation, GitHub returns you to Draftt. The integration appears under Integrations > GitHub. You don’t need an API key or personal access token.

​
What Draftt reads

The Draftt.io GitHub App has read-only access to repository contents and metadata. It cannot push code, open pull requests, or change settings in your organization. For each repository in the installation, Draftt reads:
  • Repository details: Name, visibility, and last push date
  • Dependency files: Build files and lockfiles. Draftt fetches only the files it needs to find dependencies, and fetches the full repository only if a scan needs it
Draftt then checks each dependency for:
  • End of life: Versions that have reached end of life, with the next supported version
  • Deprecation: Packages that are deprecated or archived on GitHub, with a suggested replacement when one exists

​
Verifying your connection

After setup, return to Integrations > GitHub in Draftt. The table shows the integration name, installation ID, GitHub organization ID, GitHub organization name, and date the integration was created. If Draftt can’t connect to the organization, a warning icon appears next to the integration name. Hover over the icon to see the reason, such as an authentication failure, an IP allow list restriction, or missing permissions. After the first scan finishes, your repositories appear under Code > Catalog.

​
Managing the integration

To change which repositories Draftt can read, go to Integrations > GitHub and click Configure on the integration row. Draftt opens the app’s settings in GitHub, where you can update the repository selection and save. You can also open these settings from GitHub under Your organizations > Settings > Third-party Access > GitHub Apps > Draftt.io > Configure. For details, see GitHub’s guide to reviewing and modifying installed GitHub Apps. Deleting the integration in Draftt doesn’t uninstall the Draftt.io GitHub App from your GitHub organization. To remove it completely, also uninstall the app in GitHub under Settings > Third-party Access > GitHub Apps.