Funk needs exactly one thing before it can show you anything useful: permission to read the projects you already have. Here is what that looks like end to end.

Pick the account, not the repository

Connect at the account or organisation level rather than picking repositories one by one. Funk only reads metadata, and connecting broadly means new projects appear on your board the day you create them instead of the day you remember to add them.

Check the scopes

The consent screen should list read-only permissions and nothing else. If you see a write scope, stop and tell us, because that is a bug on our side. You can revoke access at any time from the provider, and Funk will fade out the affected projects rather than showing you stale numbers.

The first score takes a few minutes

We backfill roughly ninety days of history so the first score means something. For a large organisation that can take up to ten minutes, and you can close the tab while it runs. Once it is done, every project you have access to shows up on one page, ranked, with the signals that produced each number one click away.

If you are connecting an organisation you do not own

You will need an admin to approve the read-only scope once. Send them the scope list rather than the marketing page — it is a shorter document and it answers the only question they have. Most approvals we hear about take a day, and the ones that take longer are usually waiting on a person rather than a policy.

You can connect your personal account first and add the organisation later. Nothing is lost by starting small: scores are computed per project, not per connection.

What happens in the first ten minutes

We read metadata only — commit timestamps, pull request states, deployment events, error counts. No file contents, no diffs, no source. The backfill covers roughly ninety days so the first score has something to compare against, and it runs in the background while you look around.

Projects appear as they finish backfilling rather than all at once. A large organisation can take fifteen minutes to fill in completely. A personal account is usually done before you have finished reading this paragraph.

If the consent screen lists anything other than read permissions, stop and tell us. That is a bug on our side, not a decision on yours.

If the first score looks wrong

The most common cause is bot traffic. Dependency bots, formatters and release automation all produce commits, and until we have enough history to recognise them they can make a quiet project look busy. Give it a week and the pattern settles.

The second most common cause is a project that is finished. The score is a measure of motion, and finished things do not move — there is more on that in the health score post.

Adding the rest

Connect deploys next, then errors, then issue tracking. Each one sharpens a different signal, and each one is the same read-only shape as the first. There is no configuration step between them and no order you have to follow. The score simply gets less approximate as you go.

Written by