> ## Documentation Index > Fetch the complete documentation index at: https://docs.datavendor.ai/llms.txt > Use this file to discover all available pages before exploring further. # Quality checks and going live > What runs after you submit, how a listing earns the verified badge, and how it goes live. A submitted listing enters **Checking** and locks for edits while automated checks run against its assets. Follow them on the listing page, under **Quality checks** below **Listing status**. Every kind of listing goes through the same flow. ## Read the report **Quality checks** shows the latest run as three steps. Each step with verdicts has a bar with one segment per check and a count of how many passed. Until the recommended checks run, the **Verified badge** bar ends in an empty **Recommended checks** segment, because the badge needs them. Issues are grouped under the listing or the asset they ran on; expand an issue to read why it failed. Passed checks fold into a list you can open. | Step | What it covers | Status | | - | - | - | | **Required to publish** | Mandatory checks. Every one must pass before the listing can go live. | **Running**, **Blocked**, or **Cleared** | | **Verified badge** | Every other check, including the recommended checks. Every one must pass to earn the badge. | **Running**, **Not earned yet**, or **Earned** | | **Insights** | Measurements of each asset, graded A to D. | None: insights carry no verdict | Read together, the first two steps put a listing in one of four states: * **Running**: checks are still in progress. * **Blocked**: a required check failed, so the listing cannot go live. * **Not earned yet**: every required check passed, but a badge check failed, was skipped, or has not run. The listing can go live without the badge. * **Earned**: every check passed. Buyers see the verified badge. ## Required to publish Mandatory checks are free and look for problems that would block a sale. They depend on what the listing holds. For example: | Asset | Mandatory checks look for | | - | - | | **Any listing** | Credentials and personal data, such as emails or phone numbers, in the listing text. | | **HUD tasksets** | Tasks in the taskset, and clean results from DataVendor's QA agents on the latest run. | | **Environments** | A successful build. | | **Codebases** | A readable repository copy with its Git history and captured pull requests. | DataVendor maintains the exact set, so the checks on your listing can differ from this table. A failed check, or one marked **On our side** because it could not finish on DataVendor's side, shows **Blocked** and moves the listing to **Needs attention**. ## Verified badge The verified badge, [DV quality certified](/overview/glossary#dv-quality-certified), is DataVendor's approval that a listing meets its marketplace quality standards. Buyers see it next to the title in the catalog and on the listing page, certified listings rank ahead of comparable ones, and buyers can narrow the catalog to **Verified only**. A listing earns the badge when all of these hold on the latest run: * Every required check passed. * Every other check under **Verified badge** passed. A skipped check, one that could not inspect what it grades, withholds the badge in either step. * Every recommended check that applies to the listing's assets passed. A listing with no recommended check that applies to its assets cannot earn the badge. **Recommended checks** run your environments and cost credits. Start them from the **Verified badge** step with **Run recommended checks**; the price shows beside the button before you start. Their failures are listed under **AI review**. Badge checks never block publishing. The badge belongs to the listing, not your vendor account: editing the listing or refreshing its assets removes it until the checks pass again. ## Insights Insights report where each asset sits on a measure, such as commit density or test coverage for a codebase. Measures run down the side and each asset has its own column, graded from **A**, the best, to **D**; wide listings scroll sideways. A dot means the measure does not run on that asset. Hover a grade for its reading. When a measure could not be graded and you can fix that, a note under the table says how, such as including a coverage report in the archive. Insights never block publishing or affect the badge. ## After the checks When **Required to publish** shows **Blocked**, read the reason under each issue, edit the listing, and submit it again. If a check failed on DataVendor's side, choose **Run checks again** in **Manage listing** to re-run every check without editing. When a badge check other than a recommended check fails, the listing can stay at **Needs attention** with editing unlocked. Fix it and resubmit, or choose **Skip review** in **Manage listing**: the unresolved optional checks are marked skipped and the listing reaches **Ready** without the badge. Skip review is available only once every required check has passed. A failed recommended check does not hold the listing back. Re-run it on its own from its row, at that check's current credit price, or start the recommended checks again. A listing at **Ready** publishes to the catalog with **Go live**, becoming **Active**. Editing a submitted listing returns it to Draft, removes the badge, and re-runs the checks on resubmit. If DataVendor rejects a listing outright, it shows **Rejected** and cannot go live. ## Next [Manage a listing](/sell/listings/manage-a-listing) covers what changes once it is live. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.