Activating the Plan
Connect GitHub, link an eligible repository, and activate the free Open Source plan — for a brand-new workspace or an existing one.
Last updated
There are two ways to get onto the Open Source plan, depending on whether
you're starting fresh or converting a workspace you already have. Both leave
you with a workspace on the oss plan; each project you then create in it is
linked to an eligible public GitHub repository that you pick when you create
the project.
Binding a repository grants the plan's quota — it does not by itself make anything public. Publishing a report is a separate, explicit step; see Publishing a Report.
Eligibility rules
A repository is checked against these rules each time it's linked to a project. The lifecycle section says what happens if Qualflare later finds that it no longer qualifies.
| Rule | Requirement |
|---|---|
| Visibility | Public — private repositories are never eligible |
| Fork | Must not be a fork — link the original repository |
| Archived | Must not be archived |
| License | Must carry a license GitHub can identify, and it must be on the OSI-approved list below |
OSI-approved licenses (by SPDX identifier):
MIT · Apache-2.0 · BSD-2-Clause · BSD-3-Clause · GPL-2.0 · GPL-3.0 ·
LGPL-2.1 · LGPL-3.0 · AGPL-3.0 · MPL-2.0 · EPL-2.0 · ISC ·
Unlicense · Zlib · BSL-1.0 · CDDL-1.0 · MS-PL · OSL-3.0 ·
Artistic-2.0 · NCSA · PostgreSQL · EUPL-1.2
A license file GitHub can't confidently identify (shown on GitHub as "NOASSERTION" — common for licenses like SSPL or ones with an added Commons Clause) fails this check even though the repository does have a license file. If your license isn't recognized or isn't on the list above, it isn't eligible — there's no manual override.
Two more checks, a minimum star count and a minimum repository age, are turned off: Qualflare doesn't reject a repository for its stars or its age.
Workflow: converting an existing workspace
This is a one-time, workspace-level action, and only a workspace Owner can do it. The workspace must be on the free Starter plan and have no projects.
- A workspace on a paid plan gets "cancel the paid subscription before switching to the Open Source plan". If you already pay for Qualflare, create a new workspace for the open-source repository instead.
- A workspace that is already on the Open Source plan gets "this workspace is already on the Open Source plan".
No menu item links to this page. Open it by its address.
Steps
- Go to this address, with your workspace identifier in it:
https://app.qualflare.com/workspace/<workspace-identifier>/open-source - Connect GitHub: click Connect GitHub to install the Qualflare GitHub App. This is what lets Qualflare verify a repository is eligible before granting the plan — a full-page redirect to GitHub, then back.
- Link repository: enter the repository as
owner/repo(e.g.vercel/next.js) and click Activate Open Source plan. - On success, your workspace's plan switches to Open Source immediately.
- Click Create your first project, then create a project and pick the repository in its repository picker. The repository you entered to activate the plan isn't reserved until a project is linked to it.
Activating requires an empty workspace. Every project in a workspace on the Open Source plan must be linked to a verified repository, and existing projects can't be linked retroactively — so this only works for a workspace that has zero projects yet. If you already have projects, create a fresh workspace for the open-source repository instead.
If linking fails, the form shows an inline, specific reason — see the table below for what each one means.
Workflow: creating a new Open Source workspace
A new Open Source workspace gets the plan right away, whether you create it during onboarding or later with Create Workspace on the workspaces page (workspace switcher > All Workspaces; see Create a workspace); you connect GitHub and pick a repository when you create its first project.
Steps
- Choose Open Source as the Workspace Type ("Free plan for a public GitHub project, with a shareable report page.") instead of Team.
- When you create its first project (during onboarding, at the project step), pick a repository from the org/repo search dropdown — this only lists repositories that already pass the eligibility rules above and aren't already linked to a different project. Picking one autofills and locks the project's Project Name and URL Path (the project identifier) — on this plan, they're derived from the repository, not hand-typed.
- If GitHub isn't connected yet, the same picker shows a Connect GitHub prompt inline, with the same eligibility checklist.
The GitHub App install scope is a real first-run trap. When installing the Qualflare GitHub App, GitHub asks whether to grant access to "All repositories" or "Only select repositories." If you choose the latter and don't explicitly include your target repository, the picker will show zero eligible repositories — not an error, just an empty list, because Qualflare can't see a repository the App was never granted access to.
Choose "All repositories," or make sure to explicitly select your repository during GitHub's install screen.
If a brand-new Open Source workspace's GitHub App install produces zero eligible repositories, onboarding's project step shows a back arrow. It returns you to Name your workspace, where you can choose Team as the Workspace Type and create a Team workspace instead. The Open Source workspace stays, with no projects.
Why a repository was rejected
Every failing rule is reported at once — not one at a time — so you can fix everything before resubmitting instead of hitting a new rejection on each retry.
| Reason shown | What it means |
|---|---|
| The repository must be public. | The repository is private. |
| Forks aren't eligible — link the original repository instead. | The repository is a fork. |
| The repository is archived. | The repository is archived on GitHub. |
| Add an OSI-approved open-source license to the repository. | GitHub found no license file at all. |
| The license must be OSI-approved (e.g. MIT, Apache-2.0, GPL, BSD, MPL-2.0). | A license exists but isn't on the approved list (see above). |
| The repository doesn't have enough stars yet. | The (currently disabled) star-count floor. |
| The repository is too new. | The (currently disabled) age floor. |
| "…is not visible to the Qualflare GitHub App…" | The repository isn't public, or the GitHub App wasn't granted access to it (see the install-scope callout above). |
| "…is already linked to another Qualflare workspace…" | This repository already backs a project, in this workspace or another: a repository can be linked to only one project in all of Qualflare, and deleting that project doesn't release it. |
Related
- Publishing a Report — the separate step that actually makes a report public
- FAQ — more on rejected repos and what happens if one goes private later
- Workspaces — general workspace concepts
- Changelog: Qualflare is free for open-source projects
Open Source plan
Qualflare is free for public, OSI-licensed GitHub projects, with a public report page, a README badge or banner, AI report analyses and CI upload.
Publishing a Report
Turn on a project's public report, embed a badge or banner in your README, and understand what happens if your repository ever loses eligibility.