Understand project Activity

What Activity is

Activity is the project-wide timeline of audit, Autofix, and pentest runs. It combines events from the repositories connected to one project so you can see when Guard checked health, attempted an improvement, or ran active testing.

Each vertical bar represents one recorded run. The horizontal axis groups runs by UTC day. When several runs happen on the same day, they appear from left to right in event-time order.

Activity can show up to the previous six months, starting with the first available audit when that happened more recently.

How to read the skyline

Audit bars encode two pieces of information:

• Height represents the audit score. A taller audit bar means a higher score.
• Color uses the normal score ranges: red is 0–39, yellow is 40–69, and green is 70–100.

Autofix and pentest bars do not encode a score. Both use a fixed height. Autofix is violet; pentest uses the muted neutral color. Treat these bars as evidence that a run was recorded, not as a health rating.

Every bar in this example

1. Jul 10 — Security audit, checkout-service, 34/100. The short red bar records an audit in the red score range.
2. Jul 11 — Dependency hygiene audit, workspace-client, 58/100. The yellow bar is taller because 58 is higher than 34, but it remains in the 40–69 range.
3. Jul 12 — Tests audit, billing-console, 82/100. The tall green bar records an audit in the healthy score range.
4. Jul 13 — Autofix “Dependency hygiene”, workspace-client. The violet fixed-height bar records an Autofix run. Its height is not a score.
5. Jul 14 — Pentest, checkout-service. The muted fixed-height bar records an active testing run. It does not claim that the target is secure.
6. Jul 15, left — AI readiness audit, workspace-client, 66/100. The first bar for the day is a yellow audit result.
7. Jul 15, right — Autofix “AI readiness”, workspace-client. The second bar is violet because the Autofix happened after that audit on the same day.

All repositories, dates, and results in this example are fictional.

Use filters and reports

Activity can be filtered to audits, fixes, pentests, or problems. The Problems filter keeps audit events with a score below 90; it does not include Autofix or pentest runs by itself.

In the product, a bar with an available report opens that exact run. Read the report to see the repository, evidence, findings, outcome, linked issue, or proposed pull request where applicable.

What Activity does not prove

• An audit bar is a snapshot of one completed audit, not permanent project health.
• An Autofix bar means an improvement run was recorded, not that a human merged its change.
• A pentest bar means active testing ran, not that every attack path was covered.
• A quieter timeline can mean no eligible work ran; it is not automatically a healthier project.

Use Activity to find the run you need, then use its report and evidence to decide what happened.