---
title: "Verify a codebase module page against its source commit | Proofline Help"
description: "Open a repository's Codebase page after a build publishes. Match the module's claims to its citations and check the freshness of the build before relying on the page."
url: https://proofline.sh/help/verify-codebase-module-citations/
---

[Help center](/help/)

# Verify a codebase module page against its source commit

Open a repository's Codebase page after a build publishes. Match the module's claims to its citations and check the freshness of the build before relying on the page.

## Read a page

The top of the **Codebase** page shows the published build:

-   **Commit** links to the commit every page describes. While a newer build runs, the pages keep describing this commit until it completes.
-   **Built** shows when the build finished.
-   **Verification** shows how many pages are verified. **Not verified** means each claim cites lines that exist at this commit, but Proofline has not confirmed that the lines support the claim.
-   **Credits spent** shows what the build cost.

Under **Modules**, use **Filter by path** to find a module, then open its page. A module that holds only tests is listed as **Tests, no page** and opens nothing. Each page repeats its commit and verification and lists its **Citations** at the end. A claim whose citation did not resolve at the commit is removed before the page is published. A page's text is deleted 30 days after a newer build replaces it.

## Related guides

-   [Build and read codebase pages](/help/codebase-pages/)
