Activity

The Activity page of a repository records what happened to it: which files arrived, where they came from, and what was changed in the settings.

File events

Anyone with read permission sees the file events, newest first.

Event	What it means
Deploy	A file was deployed to the repository
Replace	A deployed file took the place of one that existed
Cache	A file arrived from an upstream
Delete	A file was deleted
Index publish	The Maven index got a new incremental part
Index reset	The Maven index was rebuilt from the start

Each event names the path, the file's SHA-256 digest, and, for a replacement, the digest of the file that was there before. A deploy names the account or the token that made it; a cached file names the upstream and the URL that it came from.

Provenance of one file

The file page shows the events for that path alone, which answers the question "where did these exact bytes come from" without reading the whole log.

Because a replacement keeps the previous digest, you can tell that a file changed and what it was before, even in a repository that allows replacing files.

Settings changes

An administrator also sees the settings events.

Event	What it means
Repository created, updated, or deleted	The repository or one of its settings changed
Upstream added, updated, removed, or reordered	An upstream changed
Content rule added or removed	A content rule changed
Access granted or revoked	Someone, or a token, was given or lost access
Domain added, removed, or status changed	A custom domain changed

Passwords aren't recorded. An upstream event records only that a password was set.

What activity is for

Use it to answer the following questions:

• Did the release actually land, and which build deployed it?
• Did this file come from us, or from an upstream?
• Who made the repository public?
• Why did a dependency change without a version change?