Repository navigation
A report for the question the weekly digest does not answer — what the fleet is made of and how far behind it is — and the printing it turned out nobody had ever tried.
The dependency and technology report
GET /reports/dependencies, on the Reports page for the fleet and on each repository's own Report tab. One endpoint, one shape, two places to read it, so the two views cannot drift apart.
Four version states, never three. A dependency nobody has compared with a registry is unchecked — unknown, not up to date:
| State | Means |
|---|---|
current |
The manifest already allows the newest published release |
behind |
The registry has a release the manifest does not admit |
unknown |
Checked and not comparable — a digest, a commit, an interval, or a registry that refused |
unchecked |
Never compared with a registry |
Folding unchecked into "current" is what would turn every percentage on the page into a claim nobody verified. On a real fleet the distinction is the whole report: 5857 dependencies came back as 129 current, 61 behind, 2 unknown and 5665 unchecked. So the report says how many were never asked, names the repositories nobody has scanned rather than counting them as clean, dates the newest registry answer it is reasoning from, and explains the pins it cannot compare instead of dropping them.
Packages behind are grouped across repositories and ranked by reach, because one upgrade that clears nine repositories is different work from nine unrelated ones. Technologies stay two independent signals — languages from the hosting provider describing the code, ecosystems from the manifests describing what it depends on — since a repository can report TypeScript and carry its risk in a Dockerfile.
Printing
Ctrl+P cut the page, and two of the causes lost content rather than looking wrong. .table-scroll scrolls sideways and the dependency tables cap their height inline; a printer does neither. Measured at a 700px page, the dependency table wanted 954px of width inside a 630px box and 1511px of height inside 384px — five columns and three quarters of the rows never reached the paper.
Print now has its own layout: one column, no navigation or buttons, nothing clipped, a fixed table layout so no column can push past the sheet, headers repeated on every page a table spills onto, and rows that do not split down the middle. The window titlebar was absolutely positioned and landed on top of the rows when a window broke across pages; in print it sits in the flow. Titlebars and table headers are white text on a coloured background, which disappears entirely when Chrome drops background graphics — its default — so they print black on white, and colour is forced only where it is the information: severity badges and the bars.
Fixes
- The bar charts never had a fill.
.bar-fillis a span, and width and height do not apply to an inline box, so every bar — Overview, feed health, the new report — measured 0x0 and drew an empty track. The track showed because it is a grid item and grid items are blockified; its child is not.
Verification
1268 tests across 69 suites, green. The route was exercised live in the running container (fleet 200, scoped 200, unknown id 404, non-integer id 400), and the print layout was measured and rendered at page width. Pagination itself was not confirmed visually: this machine has no PDF rasterizer, so header repetition and row splitting rest on standard table-header-group and break-inside: avoid rules rather than on a picture.
Full changelog: https://github.com/jacksonfdam/atalaia/blob/main/CHANGELOG.md