Why is my GitHub repo not showing up?

What to do if your GitHub project is not appearing on Snyk.io

There are several reasons why your GitHub repo might not be appearing on the Snyk 'Add project' page.

1. You haven't refreshed your Snyk projects for a while
On the add project page click the 'Refresh results' link to re-sync with GitHub.

null

2. You did not grant Snyk permission to access your private projects
If the repos that you are not seeing were private, make sure you grant access to private projects.

  • Go to Settings > Integrations
  • click 'Edit settings' for GitHub
  • choose 'Public and private repos' and click update settings

3. Snyk was not able to identify your project

Snyk currently supports the following dependency file types:

  • package.json (npm)
  • Gemfile.lock (RubyGems)
  • pom.xml (Maven) 
  • build.gradle (Gradle)
  • build.sbt (Scala)
  • requirements.txt (Python)

If your dependency file is in a folder, rather than in the root of your repository, we will not be able to identify it. It is possible to add these repositories manually. 

  • On the 'Add project' page, scroll to the bottom of the page and expand the 'Add custom file location' option. 
  • Choose the repository you want to add and specify the path to the manifest file.

null

4. The repo is in a GitHub organisation that Snyk is not authorised on

You will need to revoke the Snyk permissions on GitHub and then re-connect to GitHub on Snyk.io. For full details take a look at the How do I authorise a new GitHub org? article.

5. The repo has inherited the 'Allow third party access setting'
GitHub repos that are forked from other repos use the 'Allow third party access' setting from the parent repo in all cases.

If this setting is set to not allow third parties on the parent repo then Snyk will not be able to access the forked repo.

We are working with GitHub to understand if it is possible to update this setting on the forked project.

6. You do not have admin access to the repo
If you see the following warning, it means that we need admin access to your repositories in order to set up a webhook:

null

This webhook allows us to test your PRs and ensures that we always have an accurate picture of the vulnerable state of your project. To resolve this issue you need to ask an administrator to grant you admin access to the repo via the repo's settings page (Collaboration & teams section).