> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/workspace/reports/harden-runner.md). # Harden-Runner The Harden-Runner Reports page provides visibility into how widely Harden-Runner is being applied across your GitHub organization. It helps security and DevOps teams answer questions like: * How many workflow runs are protected? * Which repositories are still unmonitored? * How has coverage changed over time? * Where should rollout efforts focus next?

### Organization Coverage This section shows how many workflow runs are currently monitored by Harden-Runner. It includes: * Coverage percentage * Monitored runs * Unmonitored runs * Total runs ### Coverage History The Coverage History chart tracks monitoring coverage over time for the selected period. Use this view to understand adoption trends across the organization. ### Repository Coverage The Repositories table provides per-repository coverage information. For each repository, you can see: * Monitored runs * Unmonitored runs * Total runs * Coverage % Repositories can be expanded to view workflow-level details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stepsecurity.io/workspace/reports/harden-runner.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.