Skip to content

Managing Assets

The Assets page is your central hub for viewing, searching, and managing all repositories connected to Mayo ASPM. This guide covers the assets table in detail, including every column, filtering options, and available actions.

The Assets Table

The assets table displays all repositories in your organization with the following columns:

Repository

The full repository name in owner/repo-name format. This column serves as the primary identifier and link:

  • Click the repository name to navigate to the asset detail page, where you can see full scan history, findings, and metadata
  • Repository names are displayed with an icon indicating the source (GitHub logo)

Type Badge

A color-coded badge indicating how the asset was added:

Badge Meaning
Integration (blue) Synced automatically via the GitHub App
Public (gray) Added manually by pasting a public GitHub URL

Branch

The default branch being monitored for this asset. Common values include main, master, or develop. This is the branch that:

  • Scheduled scans run against
  • Ad-hoc scans target by default (can be overridden)
  • Represents the "current state" of the codebase

Branch Detection

For integration assets, the default branch is automatically detected from GitHub and updated during nightly syncs. For public assets, the branch is captured at the time the asset is added.

Projects Count Badge

A numeric badge showing how many projects this asset belongs to. For example, a badge showing 3 means the asset is assigned to three projects.

Clicking the projects badge opens a modal dialog listing all associated projects by name. From this modal, you can:

  • View the project names
  • Click a project name to navigate to that project's detail page

Active Status

A toggle switch indicating whether the asset is actively monitored:

Status Behavior
Active (green) Asset is included in scheduled scans and appears in default filtered views
Inactive (gray) Asset is excluded from scheduled scans but retains all historical data

When to Deactivate

Deactivate assets for archived repositories, deprecated services, or repos you no longer want to scan on a schedule. You can still trigger ad-hoc scans on inactive assets.

Last Synced

The timestamp of the most recent metadata synchronization from GitHub. This tells you when Mayo ASPM last refreshed the repository's metadata (branch, description, visibility).

  • For integration assets, this updates during the nightly sync (2:00 AM UTC)
  • For public assets, this reflects the timestamp when the asset was added
  • Displayed in relative format (e.g., "2 hours ago", "3 days ago") with full timestamp on hover

Scans Count

The total number of completed scans for this asset across all scanner types. This gives a quick sense of how much scanning activity has occurred.

Scan Button

An action button on each row to trigger an ad-hoc scan immediately. Clicking the Scan button opens the scan configuration modal where you can select:

  • Which scanner to use
  • Which rule set to apply
  • Which branch to scan (defaults to the asset's default branch)

See Ad-Hoc Scans for full details on the scan modal.

Searching and Filtering

Text Search

The search bar at the top of the assets table performs a real-time text search across repository names. Type any part of a repository name to filter the table:

payment       → Shows "payments-api", "payment-service", "payment-frontend"
react         → Shows "react-app", "react-components"
org/repo      → Matches the full owner/repo pattern

Search is case-insensitive and matches anywhere in the repository name.

Filter Controls

Above the assets table, filter controls allow you to narrow the displayed assets:

Filter Options Description
Type All, Integration, Public Filter by how the asset was added
Status All, Active, Inactive Filter by active monitoring status
Project Dropdown of all projects Show only assets belonging to a specific project

Combining Filters

Filters are cumulative. Selecting Type: Integration and Status: Active shows only integration assets that are currently active. The search bar further narrows within the filtered results.

Clearing Filters

Click the Clear Filters button or the X icon on individual filter chips to reset the table to its default view showing all assets.

Pagination

The assets table uses server-side pagination to handle large asset inventories efficiently:

  • Page size — 25 assets per page by default
  • Navigation — Use the page controls at the bottom of the table (Previous, Next, and page numbers)
  • Total count — The total number of matching assets is displayed above the table (e.g., "Showing 1-25 of 142 assets")

Pagination respects active filters and search terms. If your search matches 8 assets, the table displays all 8 on a single page.

Asset Detail Page

Clicking a repository name in the assets table navigates to the asset detail page, which provides a comprehensive view of a single asset:

Overview Section

  • Repository name, owner, and description
  • Type badge (Integration or Public)
  • Default branch
  • Active status toggle
  • Last synced timestamp
  • Creation date

Findings Table

A paginated table of all findings associated with this asset, with columns for:

  • Severity (Critical, High, Medium, Low)
  • Title
  • Scanner type
  • Status (Open, Confirmed, In Progress, Resolved, False Positive, Accepted Risk)
  • First detected date

Scan History

A list of all scans that have been run against this asset, showing:

  • Scanner used
  • Scan status (Completed, Failed, Cancelled)
  • Duration
  • Findings count
  • Timestamp

Bulk Operations

The assets table supports bulk operations for managing multiple assets at once:

  1. Select assets using the checkboxes on each row
  2. Select all on page using the header checkbox
  3. Choose a bulk action:
Action Description
Activate Set all selected assets to active status
Deactivate Set all selected assets to inactive status

Common Workflows

Finding a Specific Repository

  1. Navigate to the Assets page
  2. Type the repository name (or part of it) in the search bar
  3. Click the repository name to open its detail page

Reviewing Inactive Assets

  1. Set the Status filter to Inactive
  2. Review which assets are not being scanned on schedule
  3. Reactivate any assets that should be monitored by toggling the Active switch

Checking Sync Status

  1. Sort the table by Last Synced column (ascending)
  2. Assets at the top have the oldest sync timestamps
  3. If an integration asset has not synced recently, check that the GitHub App is still installed on the repository's organization

Next Steps