> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub on Vortex IQ

> Monitor GitHub health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor GitHub health, cost and reliability signals, and catch incidents and runaway spend early.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=github)

<CardGroup cols={5}>
  <Card title="20">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="0">
    prepared fixes
  </Card>

  <Card title="35">
    proven workflows
  </Card>

  <Card title="1,221">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (14 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                       |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Repos (30d)**              | Watch only         | Count of repos with pushed\_at within the last 30d and archived=false.                                                               |
        | **Avg Commits / Active Repo (30d)** | Watch only         | 30d commit count / active-repos-30d; concentration of delivery across the fleet.                                                     |
        | **CI Pass Rate (30d)**              | Alert band 95 / 80 | workflow\_runs with conclusion=success / all completed runs (conclusion not null) created within 30d, x100, across the top 10 repos. |
        | **Languages by Repo Count**         | Watch only         | Repos grouped by their primary language field (nulls skipped), top 10 by count.                                                      |
        | **Median Open PR Age**              | Alert band 3 / 14  | Median of (now - created\_at) in days across all open PRs; drives vc\_pr\_age\_days (lower is better).                               |
        | **Merged PRs (30d)**                | Watch only         | Count of closed PRs with merged\_at within the last 30d (state=closed\&sort=updated) across the top 10 repos.                        |
        | **Most Active Repo (30d)**          | Watch only         | The repo with the most commits in the last 30d; value = commit count, detail = repo full\_name.                                      |
        | **Open Pull Requests**              | Watch only         | Count of open PRs from /repos/{owner}/{repo}/pulls?state=open across the top 10 repos.                                               |
        | **PR Age Alert**                    | Alert band 3 / 14  | Median open-PR age in days; fires when it crosses the vc\_pr\_age\_days band (bad at >14d).                                          |
        | **Releases (30d)**                  | Watch only         | Count of releases with published\_at within the last 30d from /repos/{owner}/{repo}/releases across the top 10 repos.                |
        | **Repositories**                    | Watch only         | Count of repos returned by /user/repos (affiliation=owner,organization\_member).                                                     |
        | **Stale PRs (>14d)**                | Watch only         | Count of open PRs whose age (now - created\_at) exceeds 14 days.                                                                     |
        | **Total Stars**                     | Watch only         | Sum of stargazers\_count across all repos.                                                                                           |
        | **Workflow Runs (30d)**             | Watch only         | Count of Actions workflow\_runs created within the last 30d across the top 10 repos.                                                 |
      </Accordion>

      <Accordion title="Grow revenue (4 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                                                                                           |
        | ------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Commits (30d)**         | Alert band 0 / -50 | Count of commits from /repos/{owner}/{repo}/commits (author date within 30d) summed across the top 10 repos; change\_pct vs the prior 30d drives vc\_dep |
        | **Deploy Cadence Trend**  | Alert band 0 / -50 | Daily count of delivery events (commits + releases) over 30d; value = 30d total, change\_pct vs the prior 30d drives vc\_deploy\_cadence.                |
        | **Deploy Stall Alert**    | Alert band 0 / -50 | Delivery-event (commits + releases) change\_pct vs the prior 30d; fires on a stall per the vc\_deploy\_cadence band.                                     |
        | **Pipeline Health Score** | Alert band 90 / 70 | 0-100 composite = 0.4 x CI pass rate + 0.3 x PR-age score (100 at \<=3d, 0 at >=14d) + 0.3 x deploy-cadence score (100 + cadence change\_pct, clam       |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                                        |
        | ----------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
        | **Daily Commits Trend** | Watch only      | Commits grouped by day over the last 30d (author date), summed across the top 10 repos.               |
        | **Open Issues**         | Watch only      | Sum of open\_issues\_count across all repos (the field counts issues plus open PRs per the REST API). |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="CI pass rate below 80%">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 CI runs is failing. At this rate, a genuinely broken change is more likely to slip through unnoticed (lost in the normal noise of failures) and developers waste time re-running or diagnosing failures that have nothing to do with their own change, slowing the whole team down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CI-001`
      </Accordion>

      <Accordion title="Delivery cadence dropped more than 50% vs the prior period">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Deploys or merges have dropped by more than half compared to the prior period. That usually means fixes and improvements, including fixes for issues this same audit has flagged elsewhere, are not shipping, which slows the whole team's ability to respond to anything urgent.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CADENCE-001`
      </Accordion>

      <Accordion title="Median open pull-request age above 14 days">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Half of open pull requests have been waiting more than two weeks. Work that is done but not merged is not delivering any value yet, and the longer a PR sits open, the more it tends to drift from the main branch, making it harder to merge later than it would have been today.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-PR-001`
      </Accordion>
    </AccordionGroup>

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **637 read** and **584 write** operations across gists, repoissuecomments, repopullcomments, userfollowings, userpackages, userpackageversions on GitHub. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=github)

    #### Proven workflow templates (35)

    <AccordionGroup>
      <Accordion title="API Contract Drift Watch">
        **For** Developer · **Ready to deploy**

        detects connector or internal schema changes before production failure.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Actionable Incident Triage">
        **For** Developer · **Ready to deploy**

        correlates errors, deploys and affected journeys and opens a pre-filled engineering ticket.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Auth Failure Triage">
        **For** Developer · **Ready to deploy**

        distinguishes expiry, scope, rate limit and upstream outage causes.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Dependency Risk Queue">
        **For** Developer · **Ready to deploy**

        surfaces relevant security/end-of-life updates with compatibility and test guidance.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Failed Job Replay Assistant">
        **For** Developer · **Ready to deploy**

        diagnoses and safely retries idempotent work while escalating unsafe cases.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flaky Test Investigator">
        **For** Developer · **Ready to deploy**

        clusters intermittent failures and ranks likely ownership and root cause.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PR Risk Summary">
        **For** Developer · **Ready to deploy**

        reports affected services, missing tests, operational risk and required approvers.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Performance Regression Bisect">
        **For** Developer · **Ready to deploy**

        correlates release changes with latency and frontend performance shifts.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Safe Fix Branch">
        **For** Developer · **Ready to deploy**

        creates a scoped branch/PR with evidence, tests and rollback notes for an approved issue.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Technical SEO Ticket Builder">
        **For** Developer · **Ready to deploy**

        translates crawl/indexation evidence into reproducible developer work.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Auto-apply Guardrail Approval">
        **For** Security manager · **Ready to deploy**

        requires security sign-off when an automation gains broader write authority.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Blocked Work Escalator">
        **For** Engineering manager · **Ready to deploy**

        detects ageing PRs/tickets and identifies the missing decision or dependency.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Change Failure Rate Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks failed deploys and highlights teams/services with worsening patterns.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Cloud Exposure Watch">
        **For** Security manager · **Ready to deploy**

        detects risky DNS, firewall, storage or edge configuration changes.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Access Review">
        **For** Security manager · **Ready to deploy**

        inventories credentials, scopes, owners, use and age; routes unnecessary access for revocation.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Engineering Dependency Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks vulnerable, unsupported or risky platform dependencies.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Executive Technology Pack">
        **For** Engineering manager · **Ready to deploy**

        translates technical risk and delivery evidence into commercial impact.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Containment Pack">
        **For** Security manager · **Ready to deploy**

        prepares reversible, scoped containment actions for human approval.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Learning Loop">
        **For** Engineering manager · **Ready to deploy**

        creates the timeline, contributing factors, actions and follow-up ownership.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Monthly Security Evidence Pack">
        **For** Security manager · **Ready to deploy**

        retains what changed, who approved it, results and rollback availability.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Privilege Drift Monitor">
        **For** Security manager · **Ready to deploy**

        alerts when repository, cloud or connector permissions exceed policy.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Risk Gate">
        **For** Engineering manager · **Ready to deploy**

        scores change size, test evidence, service health and rollback readiness before approval.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Audit">
        **For** Engineering manager · **Ready to deploy**

        verifies that rollbacks completed and downstream state returned to expected values.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Suspicious Change Correlator">
        **For** Security manager · **Ready to deploy**

        links identity, code, infrastructure and automation audit events.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Integration Risk Review">
        **For** Security manager · **Ready to deploy**

        assesses new connectors before activation and on material permission change.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Vulnerability Remediation Queue">
        **For** Security manager · **Ready to deploy**

        ranks findings by exploitability, exposure and affected revenue paths.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Weekly Delivery and Reliability Brief">
        **For** Engineering manager · **Ready to deploy**

        combines throughput, failed changes, incidents, rollbacks and ageing work.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Accessibility Regression Sweep">
        **For** Web / digital product manager · **Ready to deploy**

        monitors high-value templates for newly introduced violations.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Broken Experience Prioritiser">
        **For** Web / digital product manager · **Ready to deploy**

        combines errors, traffic and revenue impact into a ranked product backlog.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Conversion Journey Sentinel">
        **For** Web / digital product manager · **Ready to deploy**

        repeatedly tests priority journeys and captures actionable failure evidence.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Core Web Performance Guard">
        **For** Web / digital product manager · **Ready to deploy**

        detects page/template regressions and routes them to the owning team.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Post-release Regression Watch">
        **For** Web / digital product manager · **Ready to deploy**

        compares critical KPIs and technical signals before/after deploy.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Readiness Gate">
        **For** Web / digital product manager · **Ready to deploy**

        checks staging journeys, accessibility, analytics, SEO, performance and rollback readiness.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Recommendation Pack">
        **For** Web / digital product manager · **Ready to deploy**

        assembles evidence and prepares a reversible action when guardrails fail.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Script Risk Watch">
        **For** Web / digital product manager · **Ready to deploy**

        flags new, slow, failing or unapproved scripts and tags.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                            | Read operations | Write operations |
      | ----------------------------------- | --------------- | ---------------- |
      | gists                               | 3               | 3                |
      | repoissuecomments                   | 3               | 3                |
      | repopullcomments                    | 3               | 3                |
      | userfollowings                      | 4               | 2                |
      | userpackages                        | 4               | 2                |
      | userpackageversions                 | 4               | 2                |
      | enterpriscodesecurityconfigurations | 2               | 3                |
      | enterpristeams                      | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    5 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>