Skip to main content

GitHub Health: Actions costs and vulnerabilities

Open GitHub Health​

Go to Tasks → Monitor → GitHub Health. GitHub Health is in preview and disabled by default. Ask a company administrator to enable GitHub Health in Features & Permissions.

Connect a GitHub account​

  1. Go to Cloud Accounts → AI Providers and select Create → GitHub.
  2. Continue to GitHub and choose the organization or enterprise you want to connect. Use a GitHub account that can approve the installation for that organization or enterprise.
  3. Approve the Spotto Billing Reader app and return to Spotto. Repeat for each GitHub account you want to report on.
  4. In AI Providers, open Details for the connection. Expand Costs to see which months have been collected and whether the sync is queued, running, or published.

GitHub Health reads billing and workflow metadata. Detailed workflow reporting depends on the repositories the app can access. The app does not need repository contents or workflow logs.

Read the dashboard​

Use the account and date selectors to choose the scope. Overview shows cost trends and where runner minutes go. Use Repositories, Workflows, Pull Requests, and Runners & Storage to find what drove a change. Billed spend and attributed runner minutes come from different records, so incomplete workflow coverage can leave some minutes unattributed.

Recommendations points out patterns such as repeated validation, work that continues after a failure, and usage above included minutes when the billing data supports it. The cost shown is context for the recommendation. It does not represent guaranteed savings.

Review vulnerabilities​

The Vulnerabilities tab requires Security view access. It shows open Code Scanning and Dependabot findings from repositories accessible to the GitHub App, when those scanners and their read permissions are available. Use severity, scanner, and repository filters to narrow the list. If you can manage alerts, use Create Alert to configure notifications by severity.

Troubleshoot coverage​

  • GitHub setup is unavailable. Ask your Spotto administrator to configure the Billing Reader app for your environment.
  • The connection has partial coverage. In Details, check which source was unavailable. Billing, workflow details, Copilot, and each vulnerability scanner can have different coverage.
  • There are no vulnerabilities in the table. Check scanner access and sync status before interpreting an empty table as a clean scan.

For Copilot usage reporting, see AI Usage.