Entire starts recording a signed history of branch and tag changes inside each repo

Entire, the Git hosting service started by former GitHub chief executive Thomas Dohmke, is now automatically keeping a signed history of branch and tag changes inside the repositories it hosts.

The record is called a reference state log, or RSL. It follows gittuf, an open standard being incubated at the Open Source Security Foundation (OpenSSF). Entire says it’s the first Git forge (a service, like GitHub, for storing and reviewing code) to maintain this log on the server automatically, with no change to a developer’s usual Git commands.

On Entire-hosted repositories, updates to default branches and tags are now written into the repo as they happen. Developers can inspect that history with an open-source plugin for the Entire command-line tool, or verify it with gittuf itself.

“We believe this history belongs in Git itself, where developers can inspect it, verify its integrity, keep track of how it changes over time, and take it with them wherever they want their repo to be hosted.”

— Entire, in its announcement of reference state logs

Today, Entire is the first Git forge to introduce reference state logs to secure your repositories. 🔐

Following the open gittuf standard, Entire stores a cryptographically verifiable, append-only ledger of Git ref changes, directly in the repo. Your code, your sessions, and now your audit log, all in one place. 🤝

https://t.co/B9FOupq5kp

— Entire (@GoEntire) November 10, 2026

Why a log of pointers matters

In Git, a branch or a tag is a pointer: a name that points at a particular snapshot of the code. Those pointers can be moved. A force-push can make a branch point at a different history. A release tag, which people often treat as a fixed label for a published version, can also be moved, deleted or recreated. Git will show you where the name points now, not necessarily where it pointed yesterday.

The company’s blog walks through a simple case. A tag called v0.4.2 was created, then deleted, then recreated against a different snapshot. Looking at the tag afterwards would only show its new target. The reference state log still showed the three steps: created, deleted, recreated.

That sort of rewrite has already been used in a real attack. In March 2026, attackers used compromised credentials at Aqua Security, the maintainers of the widely used Trivy vulnerability scanner. According to Aqua’s official advisory, they force-pushed 76 of 77 version tags in the aquasecurity/trivy-action project to malicious commits designed to steal credentials. The tag names stayed the same; what they pointed to did not. Entire says a reference state log wouldn’t have blocked that kind of push, but it would have made the rewrite much harder to hide.

How the log works

1. You push a branch or tag in the usual way. There’s nothing extra to configure, and no signing keys to manage.
2. Entire appends a numbered entry to a log stored in the repository itself, at refs/gittuf/reference-state-log. The entry records which pointer moved and where it now points, and is built on the entry before it, forming a chain.
3. The primary Entire cluster that handled the push signs the entry, and records who pushed the change and when. Those who-and-when fields are assertions from the signer; verification itself relies on the signatures and the repository’s policy.
4. You can fetch the log with the entire-rsl plugin and inspect a branch, tag or checkpoint. If a tag has moved, the plugin warns you.
5. If the remote log no longer extends the history you’ve already fetched — if it looks like a replacement rather than an addition, the plugin leaves your local copy untouched and reports that the histories have diverged.

A typical inspection looks like this, after installing the plugin and refreshing the log:

entire plugin install rsl
entire rsl refresh
entire rsl tag v0.4.2 --fetch

Recording a tag in the log doesn’t guarantee it will verify. Official docs say unsigned tags, lightweight tags, and tags signed by other keys fail verification, even when the log entry’s own signature is valid. Today, only Entire can change the repository’s gittuf signing policy, which currently lists the cluster keys allowed to sign log entries. Entire says gittuf already has ways to control who can update specific references, and that more on that is coming.

Who it’s for, and what it costs

The log is live for repositories hosted natively on Entire. New Entire-hosted repositories already include a gittuf policy and an initial log entry. Official docs also cover inspecting Entire checkpoints, which are saved records of an AI coding agent’s session tied to a commit, when those have been captured and pushed.

During early access, Entire’s pricing page says code hosting, Trails, session storage, Continuous Memory, agentic search and the Entire CLI have no charge. The company bills only for agent usage, at the published rates of the model providers (including Anthropic and OpenAI), using prepaid credits. Official billing docs say each billing account is meant to get a one-time US$100 trial credit when a verified card is added, with no payment taken at that point. The trial ends after US$100 of usage or 90 days, whichever comes first. Those new trial credits are temporarily paused because of demand.

Bought credit starts at US$10 and expires 365 days after purchase. If the balance hits US$0, agents stop until more credit is added. Other features stay free. For custom enterprise requirements, Entire points teams to [email protected].

What Entire is

Entire is a new place to host software projects, built for teams that use AI coding agents (programs that write and change code) alongside human developers. Dohmke left GitHub and co-founded the company. It raised US$60 million in seed funding in February 2026 and opened the forge to developers on 26 October 2026.

A Git forge is the familiar combination of a Git server and a website for reviewing and shipping code. GitHub is the best-known example. Entire is offering itself as an alternative, and also lets teams mirror existing GitHub repositories onto its network.

How the rest of the platform works

Private repositories can be hosted in a region of the team’s choice. At launch, Entire listed the United States, the EU, India and Australia; it has since announced data residency in the United Kingdom, Singapore and Brazil. The company says its source-control server can push up to 89 times faster than GitHub and six times faster than Cursor Origin, based on its own benchmarks.

Instead of reviewing a pull request alone (the usual list of changed lines), the platform uses Trails. A Trail keeps the goal of the work together with automated evals: checks scored by agents on every push. Agents can loop on the findings, while a person watches progress. Entire says developers can merge when those checks are satisfied, without having to read every line. Teams can still require a person’s sign-off, or passing tests, before code goes in.

Continuous Memory stores agent session logs (the prompts and decisions behind a change) in the repository, so later agents can search them. Entire says a codebase graph can cut token use by up to 71% in its testing, and an “agentic brain” turns past sessions into memories agents can query. For builds and tests, it’s partnered with Buildkite and Depot.

Public repositories and self-hosted Git nodes are listed as upcoming features. A guide to installing the log plugin and verifying a repository is on Entire’s docs. Because the log is stored as ordinary Git objects, Entire says it can be fetched with Git-compatible tools and can travel with the repo if it’s hosted somewhere else.