Navigating the StretchDev Dashboard

Overview

The Dashboard is the first thing you see when you open StretchDev and the fastest way to gauge the health of every project in your workspace. It rolls up four headline counts, shows the mix of languages across your repositories, and reports whether the analysis engine is available. It is entirely read-only — nothing on the Dashboard changes your data — so it's safe to check as often as you like.

The four headline cards

Across the top of the Dashboard are four cards, each a single number scoped to your organization:

1. Projects — the total number of repositories you've connected.
2. Scans — the total number of analysis runs ever recorded across all projects.
3. Failed gates — how many stored scans did not pass their quality gate. A number above zero means at least one recorded change fell short of policy.
4. Open vulnerabilities — the count of vulnerability-type issues that are still open across all scans. This is your single most important security number.

How to read the Dashboard

1. Start with Open vulnerabilities. If it reads 0, no known security findings are outstanding. If it's higher, treat it as a to-do list.
2. Check Failed gates next. A rising failed-gate count tells you changes are being scored against policy and coming up short — a prompt to review recent scans.
3. Scan the language mix. The repository breakdown by primary language shows where your codebase's weight sits (for example, mostly TypeScript with some Python). Use it to sanity-check that projects are tagged with the right language.
4. Confirm the engine is available. The engine status area shows whether the analysis engine is enabled. If it reports disabled, new scans, gate previews, and release-risk scoring won't run until an administrator turns it on — but all your existing data still displays.

Example

You open StretchDev on a Monday. The Dashboard shows 12 Projects, 340 Scans, 3 Failed gates, and 2 Open vulnerabilities, with the engine status reading enabled. You click through from the Open vulnerabilities card to the Scans tab, open the two most recent scans with vulnerability findings, and assign them for the week. The three failed gates turn out to be duplication threshold misses on a legacy repo — lower priority, but now visible. In under a minute you've triaged the whole workspace.

Tips

• Treat Open vulnerabilities as a target of zero; every non-zero value is worth a look.
• If Failed gates climbs but no one is complaining, your gate policy may be stricter than your team's real standard — revisit it under Quality.
• The Dashboard counts everything in your organization, not just your own projects, so it's a good shared team view.
• If a card unexpectedly reads 0, confirm you're in the right workspace/organization — data is tenant-scoped.

Troubleshooting

• Every card shows 0 on a workspace that has data. You may be viewing a different organization than the one that owns the projects. Switch to the correct workspace.
• Engine status shows disabled. Read features still work; ask an administrator to enable the analysis engine so you can run new scans and gate previews.
• Counts look stale. The Dashboard reflects stored records; refresh the page to re-pull the latest counts after a scan completes.