⚙️ How to Set Up SourceCred

In this guide you'll find information about setting up your own instance of SourceCred to generate Cred scores for your community and/or project.

Before you start

If you’re not quite ready to create your own instance, check out our introduction or Getting Involved guides.

Before getting started, some things you’ll need to know:

  • SourceCred is organized around “instances.” When you create an instance of SourceCred for your community/project, it will collect data and generate “Cred scores” for each individual contributor based on the available data about the work you've all been doing.
  • Every SourceCred instance needs data about contributions. This information comes from the SourceCred plugins which “scrape” data from a platform to use in calculating Cred scores. Currently, the available plugins include Discord, GitHub, and Discourse. For now, your community will need to be using at least one of these platforms in order to get meaningful Cred scores.
  • Setting up a SourceCred instance is fairly technical. You’ll need to be comfortable using the terminal, installing packages from NPM, and be familiar with the basics of Git and GitHub.

If you’re interested in SourceCred but lack the technical chops, you can still get involved on our Discord or Discourse forums to learn more, ask questions, and contribute to the project.


Everything you need to know about setting up a SourceCred instance can be found in the template-instance repo, which is set up to be a good starting point for configuring SourceCred.

Every SourceCred instance is a directory, tracked by Git, with some conventions around where files are stored. For example, sourcecred.json specifies which plugins are active, and config/plugins has a folder for every individual plugin, with that plugin’s own configuration.

Once SourceCred is installed, you’ll want to configure the instance to suit your community. First, take a look at the installed plugins listed in sourcecred.json, and remove any plugins that you won’t be using. Then, for each plugin, update its plugin config.json file so that it will load your community’s data instead of the example data.