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.
Last updated
Binding a project to a GitHub repository (see Activating the Plan) grants the Open Source plan's quota. It does not, by itself, publish anything — a bound project can stay completely private. Publishing is a second, deliberate step, and each project in an Open Source workspace chooses independently.
Turning it on
Steps
- Go to Project Settings → General for the project you want to publish.
- Find the Public report toggle and turn it on.
- In the Publish report dialog, type the project identifier and select Publish Report.
- Your report is now live at
https://reports.qualflare.com/p/<project-identifier>/launches. Anyone can open it without signing in, and search engines can index its launch list. - Turn the toggle off at any time to unpublish. The report goes offline, and the runs it showed stay hidden even if you publish again. Your project's launches and results are not affected. Cached pages can stay visible for up to about an hour.
A public report shows only launches uploaded while it is published, for
example with qf <identifier> collect. Launches from before you published don't appear,
and neither do launches you start in the app. Unpublishing hides every run on
the report for good: if you publish again, the report starts empty and shows
only new uploads.
The Public report section appears for projects in workspaces on the Open Source plan. A project that is still public after its workspace leaves the plan also shows it, with only Unpublish (see below).
What viewers see
A published report shows your project's name, description, and overall pass rate, followed by a table of launches — run number, timestamp, git branch, commit, duration, and pass/fail status. Clicking a launch opens a per-test breakdown. No sign-in is required, and it's entirely read-only.
Every public report page also carries a link back to Qualflare (in the header and footer) framed as "free for open source" — the same growth loop your own badge or banner participates in.
Embeddable badge
A compact, shields.io-style status image for a badge row at the top of your README:
[](https://reports.qualflare.com/p/<project-identifier>/launches)For what each badge value means and every public URL, see Public reports and badges.
Embeddable banner
A wider card — project name (or, if your repository is linked, its
owner/repo name instead of whatever the project is called inside
Qualflare), pass rate, run count, flaky-case count, last-run time, and a
GitHub-activity-style grid of recent runs:
[](https://reports.qualflare.com/p/<project-identifier>/launches)The banner is a single image, not a light/dark pair. GitHub does support a
#gh-light-mode-only / #gh-dark-mode-only technique for theme-adaptive
README images, but it depends on the URL fragment surviving GitHub's camo
image proxy — which it doesn't for an externally-hosted image like this one.
The banner's colors are chosen to read fine on both a light and a dark GitHub
page instead, so don't try to build your own light/dark pair with that
technique; both images will just show at once.
Badge or banner? The badge is a compact chip that reads naturally alongside other status badges (build, license, version). The banner is a richer, standalone summary — better suited to its own line near the top of a README, where there's room for it.
Both images update automatically as new launches come in — there's nothing to regenerate or re-embed after your first run.
Quota and plan limits
Each limit of the Open Source plan is a fixed number, counted per workspace:
| Limit | Cap |
|---|---|
| Projects | 25 |
| Team members | 50 |
| Test cases | 50,000 |
| Test suites | 2,000 |
| Shared steps | 1,000 |
| Test plans | 1,000 |
| Test reports (launches) per month | 20,000 |
| Storage | 10 GB |
At a limit, Qualflare refuses the request that would go past it, and a workspace with more members or projects than the plan allows is frozen until it fits. See What happens at a limit and A frozen workspace. The usage screen counts test case attachments and the files uploaded with test runs against storage. When storage is full, new files are refused and results are still saved. See When storage is full.
AI and analysis features on this plan:
| Feature | Open Source plan |
|---|---|
| AI report analyses | 100 per month |
| Flaky test detection | Included |
| Quo messages | 100 per month |
| AI case suggestions | 10 per month |
| AI coverage analysis | 10 per month |
| AI step generation | 10 per month |
| Quo Pro model | Not included |
| AI failure clustering | Not included |
| AI Insights (test suite optimization) | Not included |
One test report is one run, such as an upload or a launch you start in the app, regardless of the number of individual test results it contains. Test report and AI-analysis allowances apply per workspace, not per seat, and reset monthly even on annual billing. They are not retention limits. An idempotent retry of an existing upload does not consume another report. Reaching the analysis allowance skips further analyses until reset; uploaded results remain available and uploads within the separate report allowance continue.
See Plans and limits to compare it with the paid plans.
The suspend-and-restore lifecycle
Eligibility is checked when a repository is linked. If Qualflare later confirms that a linked repository no longer qualifies (it went private, was archived, or its license changed), this is what happens:
- A transient check failure never counts against you. If GitHub is temporarily unreachable or returns an error, that's tracked separately and never starts the countdown below — a GitHub outage doesn't suspend every Open Source project on the platform at once.
- A definitive failure starts a 7-day grace period. Once a repository is confirmed ineligible (not just a flaky check), you have 7 days to fix it before anything changes.
- After 7 days with no fix, the project is suspended automatically. Its public report goes offline and your README badge shows no runs; the project itself isn't deleted. Your Public report setting is kept, so if the project is restored, the report comes back without publishing it again.
- If the repository becomes eligible again — at any point, even after suspension — it's restored automatically. There's no support ticket to file and nothing to manually re-request; fixing the underlying issue (e.g. making the repo public again) is enough.
Qualflare doesn't email you when a repository stops qualifying, so check your repository's visibility, archive status and license before you change them.
A workspace that's downgraded off the Open Source plan after publishing lands in a reduced state: the report stays public, but the Public report section only offers Unpublish — you can take it down, but it can't be republished from there without moving back onto the plan.
Related
- Activating the Plan — eligibility rules and the linking flow
- Setting Up CI — get real launches showing up on the report
- FAQ — what happens to a report that goes dark, and other common questions
- Changelog: Public test reports get their own site, previews and a README banner