---
title: "Repository Insights for Client Websites | Unolia"
description: "GitHub and GitLab repositories linked to client projects: commits with real authors, CI runs with verdicts, and a dependency diff on every commit with release notes in place."
url: "https://unolia.com/features/repository-insights"
locale: "en"
---

# Know what changed. Without reading the code.

Unolia links GitHub and GitLab repositories to their client projects and turns pushes into a story anyone can read: the commit, its author, the build result and the packages it changed.

## What are Repository Insights in Unolia?

Repository Insights links your GitHub and GitLab repositories to client projects, each repository finding its project automatically. Commits arrive with their author matched to your team, CI runs arrive with their verdict, and every commit carries a diff of the packages it changed across composer, npm and pnpm, with release notes readable in place and known vulnerabilities flagged. Version history and license detection join on higher plans.

## The moments this changes

### The afternoon it broke

The client calls at 15:40. The project page shows one commit at 14:12, a green build and a major framework bump. You know where to look before you have opened a single file.

### The PM who answered

A client asks whether the fix shipped. The project manager reads the commit, the green build and the deploy, and answers in the same minute. No developer was interrupted.

### The sneaky major

A routine-looking push carried a whole major version. The diff flagged it amber, the release notes were read in place, and the breaking change was tested before any client saw it.

## From push to plain language

### Connect GitHub or GitLab

Repositories find their client project on their own, and the history starts filling in.

### Let the story build

Commits, build runs and dependency diffs arrive as the team pushes. Nobody files anything.

### Read it, whoever you are

Support reads the story in plain rows. Developers deep-link into the code when it matters.

## What changed, who changed it, did it pass.

The next time a client site misbehaves, the first stop is the project page, where the afternoon commit, its build verdict and its package bumps are already lined up in plain rows.

- Commits signed by the teammate, not a username.
- Every build run lands with its verdict.
- Each commit carries its dependency changes.

## Every commit confesses its packages.

A push that bumps a framework a whole major should not look like every other push. The diff names each changed package, grades the jump, flags known vulnerabilities and hands you the release notes without leaving the page.

## Written by Marc, not by mlefebvre42.

Unolia matches commit authors to the people on your team. Project managers read names they know, clients hear answers instead of usernames, and when a change needs explaining you know exactly who to ask.

## When a deploy breaks, your AI already knows the timeline.

Connect an AI agent to Unolia and it reads a deploy the way you do: the commit, the packages it bumped, the build verdict and what shipped when. Its first guess starts from what changed, not from a blank page.

## How this grows with your plan

| Plan | Value |
| --- | --- |
| Developer | Repositories, commits, build runs and dependency diffs. |
| Freelancer | Security audits across every dependency. |
| Startup | Version history and license detection. |
| Business | Agency scale: 50 seats, custom roles and synced access around the code. |

## Related feature pages

- [Website Operations](/features/website-operations)
- [Security and Maintenance](/features/security-maintenance)
- [Agency Activity Log](/features/agency-activity-log)

## Know what changed before you debug the client site.

Join the waitlist and give every client site a history the whole agency can read.

[Join the waitlist](https://app.unolia.com/register)