# Open Source FAQ

Source: https://docs.qualflare.com/docs/open-source/faq · Last updated: 2026-11-06

Common questions about the Open Source plan — rejected repositories, reports going dark, moving projects, and badge vs. banner.

## Why was my repository rejected?

The rejection message names every failing rule at once — see the full
[eligibility rules and rejection-reason table](https://docs.qualflare.com/docs/open-source/activating#why-a-repository-was-rejected).
The most common one isn't a rule at all: the GitHub App was installed with
"Only select repositories" and the target repo wasn't included, which shows
up as zero eligible repositories rather than an explicit error. Reinstall
with "All repositories," or add the repository to the App's selection.

## My report disappeared — what happened?

If you or another maintainer turned off **Public report**, every run already
on the report is hidden for good, and publishing again starts it empty. If
your repository stopped passing the eligibility rules (it went private, was
archived, or its license changed), Qualflare can suspend the project after a
7-day grace period: see
[the suspend-and-restore lifecycle](https://docs.qualflare.com/docs/open-source/publishing#the-suspend-and-restore-lifecycle).
A suspension deletes nothing, and fixing the repository brings the report back.

## Can I move a project to a different workspace?

A repository binding is tied to one workspace at a time — the same repository
can't back two workspaces' plans simultaneously. Moving a project's binding
to a different workspace isn't a self-serve action; contact support if you
need this.

## Does publishing cost anything, or expose private data?

Publishing is part of the free Open Source plan. Workspaces on other plans
can't publish. You can turn the **Public report** setting off at any time, and
your launches stay in your project. A public report only shows launches
uploaded while it is public.

Anyone can open a public report without signing in, and search engines can
index its launch list. It shows:

* **Project:** name, description and linked GitHub repository.
* **Launches:** number, status and result counts, start and end time,
  framework, platform, OS, browser, language, branch, commit, CI provider,
  build number and pull request number.
* **Tests in each launch:** test and suite names, case number, priority,
  whether the test is automated, status, duration, flaky and retry details,
  and the full failure message and stack trace.

A public report never shows test case steps or descriptions, defects,
attachments, tags, environments, milestones, test plans, launch properties or
metadata, CI run URLs, AI summaries, or captured stdout and stderr.

> **Warning:** Failure messages and stack traces are published exactly as your tests report
> them. Before you publish, make sure your tests don't print tokens, passwords,
> internal URLs or personal data in assertions or error messages.
>
> Turning publishing off hides every run already on the report for good. If you
> publish again, the report starts empty.

## What if my license isn't on the approved list?

Then the repository isn't eligible for the Open Source plan — there's no
manual override or appeals process. The full list is in
[Activating the Plan](https://docs.qualflare.com/docs/open-source/activating#eligibility-rules). If your
project changes its license to one on the list, it becomes eligible on the
next check.

## Badge or banner — which should I use?

The badge is a small, shields.io-style chip — use it if you already have a
row of status badges (build, license, version) at the top of your README and
want to add one more. The banner is a wider, richer summary with a recent-runs
trend grid — use it as its own line when you want more than a single status
chip to convey. Both link to the same live report and update automatically;
nothing stops you from using both.

## Do I need to install a separate GitHub App for CI uploads?

No. The Qualflare GitHub App you install while activating the plan is the
same GitHub integration listed on your workspace **Integrations** page.
Qualflare uses it to check that your repository qualifies, and a project can
also use it to create GitHub issues. Uploading test results in CI doesn't use
it: use the `qualflare-action` GitHub Action or the `qf` CLI with an access
token. See [Setting Up CI](https://docs.qualflare.com/docs/open-source/ci-setup).

## Related

* [Activating the Plan](https://docs.qualflare.com/docs/open-source/activating)
* [Publishing a Report](https://docs.qualflare.com/docs/open-source/publishing)
* [Troubleshooting](https://docs.qualflare.com/docs/faq/troubleshooting) — general (non-OSS-specific) issues
