Application Portfolio

The Application Portfolio gives you a unified view of every code repository across all connected organizations. It aggregates health scores, application types, tech stacks, backup status, and dependency health into one dashboard — your bird's-eye view of a client's entire software estate.

What Is an Application Profile?

Every repository in The One Code has an Application Profile — a rich metadata record that's built from AI analysis of the repository's file tree, source code, and configuration files.

An Application Profile contains:

Classification

• App type — web-app, api, mobile-app, library, cli, infrastructure, script, documentation, or unknown
• Tech stack — detected technologies (e.g., React, Azure Functions, PostgreSQL, Docker)
• Frameworks — detected frameworks within each technology
• Languages — detected programming languages with percentage breakdown
• Hosting platform — detected hosting provider (Azure, AWS, GCP, Vercel, etc.)

Health Signals

• Health score (0–100) — composite signal from commit recency, issues, dependency freshness, and security
• Technical debt score (0–100) — from the Optimize module analysis
• Security score (0–100) — from secret scanning and access audit results
• Last commit date — most recent push to any branch
• Last deploy date — last detected deployment (if CI/CD is configured)
• Commit frequency — active, maintained, stale, or abandoned
• Contributors — number of contributors
• Open issues — count of open GitHub issues
• Open PRs — count of open pull requests

Dependency Summary

• Total dependencies
• Vulnerable dependencies
• Outdated dependencies
• License issues

Business Context (manually set)

• Description
• Business purpose
• Data classification (public, internal, confidential, restricted)
• Compliance tags
• Owner name

Backup Status

• Backup status (active, paused, error, never)
• Last backup date
• Backup size

The Portfolio View

Navigate to Portfolio from the left sidebar to see all application profiles across your tenant.

Filtering and Sorting

The portfolio view can be filtered and sorted by:

Filter	Options
Org	Filter to a single connected organization
Status	Active, error, stale, archived
App type	web-app, api, library, etc.
Commit frequency	Active, maintained, stale, abandoned
Health	Healthy (score ≥70), Warning (40–69), Critical (<40)
Backup status	Active, error, never, paused

Sort by health score, technical debt score, last commit date, or alphabetically by name.

💡Filter by "abandoned" commit frequency to find dead app candidates. These are great starting points for a cleanup conversation with your client.

Portfolio Summary

At the top of the portfolio view, a summary panel shows aggregate stats:

• Total apps across all connected orgs
• Health distribution — how many are healthy vs. warning vs. critical
• Tech stack breakdown — which technologies appear most frequently
• App type breakdown — proportion of web apps vs. APIs vs. libraries
• Average health score across all repos
• Total vulnerabilities across all dependency audits
• Total outdated dependencies
• Backed up percentage — how many repos have active backup coverage

Per-Client Grouping

The By Client view groups application profiles by client_id. When you've tagged repos with a client, this view shows a client-by-client breakdown of their software portfolio — useful for client-facing reviews.

To tag a repo with a client:

1. Navigate to the repo detail page
2. Click Edit Profile
3. Set the Client field to the CRM client ID
4. Save

The Repository Detail Page

Click on any repository in the portfolio to see its full detail page. This is the command center for a single repository.

Detail Page Sections

Overview — App type, tech stack, health score, last commit, contributor count, open issues and PRs.

Backup — Backup status, last backup date, backup size, and a link to the backup timeline. Trigger a manual backup from here.

Analysis — Links to trigger or view AI documentation, secret scans, dependency analysis, and tech debt analysis.

Documentation — List of generated documents for this repo, with links to view and refresh each one.

Security — Latest secret scan results and latest access audit findings that affect this repo.

Dependencies — Summary of direct dependency count, vulnerable count, outdated count, and license issues. Link to the full dependency tree.

Optimization — Current tech debt score by category and a link to the full debt report and migration recommendations.

Settings — Configure backup schedule, retention period, data classification, owner, and business purpose.

Application Health Score

The health score is a composite 0–100 signal computed from:

Signal	Weight
Commit recency	High
Open issue count	Medium
Dependency freshness	Medium
Security findings	High
CI/CD presence	Low

Score interpretation:

• 70–100 — Healthy. Well-maintained, no critical issues.
• 40–69 — Warning. Noticeable concerns worth monitoring.
• 0–39 — Critical. Needs immediate attention.

The health score is displayed as a colored badge throughout the UI:

• Green (healthy)
• Yellow/amber (warning)
• Red (critical)

Setting Business Context

The business context fields on an application profile help you communicate with clients about non-technical aspects of their software estate:

Description — A plain-language description of what the app does. Can be populated from the README by the AI, or set manually.

Business Purpose — Why this application exists from a business perspective. Used in QBR reports.

Data Classification — How sensitive the data processed by this app is:

• public — No sensitive data
• internal — Internal company data
• confidential — Client or commercially sensitive data
• restricted — Regulated data (healthcare, financial, government)

Compliance Tags — Free-form tags for compliance frameworks that apply (e.g., hipaa, pci-dss, sox).

Owner — The person responsible for this application. Useful when generating reports or escalating issues.

The data classification and compliance tags feed into compliance reporting and the regulatory classification feature.

Editing Profile Fields

Some profile fields are set manually (business context) and some are populated by AI analysis (tech stack, health scores). You can override AI-detected fields:

1. Navigate to the repo detail page
2. Click Edit Profile
3. Update any of the editable fields (backup schedule, data classification, owner, business purpose, compliance tags)
4. Click Save

Tech stack and AI-detected fields are refreshed on the next analysis run — manual overrides to non-AI fields persist.

Portfolio Use Cases for MSPs

Monthly health review — Use the portfolio view at the start of each month to check for repos that have moved into Warning or Critical health. Address issues before clients notice.

Client onboarding — After connecting a new client's org, use the portfolio summary to understand what you're working with: how many apps, what tech stacks, which need immediate security attention.

QBR preparation — Use the portfolio summary stats — health distribution, vulnerability counts, backed-up percentage — to populate the Application Review report for the client's quarterly business review.

Dead app cleanup — Filter by "abandoned" or low health score to identify repos that should be archived or decommissioned, then schedule a cleanup conversation with the client.

Compliance scope — Use the data classification and compliance tags to understand which repos fall under regulated frameworks, then prioritize compliance evidence collection for those repos first.