github getnora-io/nora v1.4.5

one hour ago

[1.4.5] - 2026-11-15

Added

  • Composer (PHP) registry (#1027) — NORA hosts and proxies Composer 2 packages. It is off by default: enable it with [composer] enabled = true or NORA_COMPOSER_ENABLED=true (NORA_REGISTRIES_ENABLE=all includes it). With repositories pointing at http://nora:4000/composer, composer require, install and update fetch from Packagist, or from the upstreams in [composer] proxies tried in order, through NORA: package metadata is cached as the upstream sent it and served with every download URL rewritten to NORA, and an archive is fetched only from the URL the upstream's metadata lists for that version and reference, then cached with its checksum verified. Packages are published with PUT /composer/packages/upload/{vendor}/{package}/{version} (the zip as the body, versions immutable), and a package with any uploaded version is served only from its uploaded versions, never merged with an upstream's. composer audit is forwarded to the upstream's advisories API; a hosted or internal name is never sent, and an upstream that cannot be read, or offers advisories only inside its metadata, is a 502, not a clean report. Curation names a package by vendor/package: blocklist, allowlist, minimum release age, digest quarantine and internal namespaces apply. github_token lifts the 60 requests an hour GitHub allows an anonymous client for Packagist's archives, and, with curation on, NORA lists only versions it serves an archive of and no VCS source, so Composer cannot clone a release curation refused; without curation, keep_source = false drops the sources. The web UI lists the packages and, per package, each version as hosted or cached. With several upstreams, a package belongs to the first upstream that has either of its two metadata documents, cached or answered, and both documents and the archives come from that upstream; an upstream that fails (unreachable, 5xx, 401, 403, 429, or an answer that is not Composer metadata) ends the search: its cached copy is served stale (serve_stale), otherwise the answer is 502 (429 for a rate limit), and no later upstream's package of the same name is served. An archive a composer.lock names keeps installing from NORA's cache after the branch it came from moves on, under the same curation and release-age checks. Not in this release: Composer 1, search, nora mirror and nora import, retention, VCS sources, uploading branch versions and deleting a version.

Changed

  • Maven directory pages come from the repository index (#1216) — /ui/maven and its directory pages listed storage and read every file's metadata on each visit (0.6 s a visit with about 4000 versions on local storage, 11–12 s on S3); they now read the in-memory repository index, and a version page lists its files in one listing. The count shown per directory is now the count of primary files, as the dashboard and /api/ui/stats count them: checksum files and maven-metadata.xml are no longer counted. An upload, an uploaded checksum or maven-metadata.xml, and metadata cached from an upstream show on the pages at once, including one that lands while the index is being rebuilt.

Fixed

  • A Terraform provider or module asked for on a cold cache resolves from the upstream (#1150) — a provider's download metadata and a module's source address were stored in the background after NORA answered, and Terraform asks for the archive about 80 ms later; when that write had not landed, another replica answered, or the entry was evicted, a provider file fell back to a constructed releases.hashicorp.com address (a 404 for every provider hosted elsewhere, and past a NORA-to-NORA chain) and a module source was 404. On a miss NORA now asks the upstream for the file's download metadata, or the module's download endpoint again, and fetches only what it gives; nothing is guessed. A provider file whose URL carries a query (a signed link) or a fragment, or a percent-encoded file name, is matched by the file name of the URL's path and fetched with the URL whole. The file links NORA answers in the download metadata and the network mirror name each file by that path, without the upstream URL's query or fragment, which NORA keeps and sends when it fetches the file. A module source whose upstream answers without X-Terraform-Get is a 502, as the module download already answered, not a 404 a client reads as a missing module.
  • A Docker upstream that rate-limits NORA is a 429 that says so, not a missing image (#1191) — when an upstream answered 429 TOOMANYREQUESTS (Docker Hub over its pull limit), a manifest or blob NORA did not have cached was answered 404 MANIFEST_UNKNOWN / BLOB_UNKNOWN, so docker pull printed manifest unknown for an image that exists, no client retried, and the Retry-After was dropped. Such a miss is now 429 with Retry-After and an OCI TOOMANYREQUESTS body that names the upstream and the wait; docker pull prints toomanyrequests: …, and containerd, BuildKit, skopeo and podman retry it (skopeo and podman after the Retry-After). The wait is the upstream's Retry-After in seconds, at most 60 s (skopeo and podman wait no longer); without one in seconds it is 30 s. Until it has passed NORA does not ask that upstream again: containerd and BuildKit retry a 429 at once, five or six times, and each retry would have gone to the upstream that is already refusing. In the fallback chain the limited upstream is skipped, as one with an open circuit breaker is, and the next one can still serve the image; when none serves it, the 429 decides over another upstream's 404, since the image may be on the limited one. A 429 does not count toward opening the circuit breaker. The wait is kept per NORA process, as the breaker is. A 429 from an upstream's token server is still answered 502.
  • NuGet search and autocomplete work from dotnet and Visual Studio (#1215) — the service index listed search and autocomplete under bare types, while NuGet clients look them up by a versioned type only, so dotnet package search and Visual Studio said "The source does not have a Search service!"; both are now also listed under /3.0.0-beta and /3.0.0-rc, as nuget.org lists them. GET …/autocomplete?id=<package> lists that package's versions instead of package IDs, and the @id a search result gives for a version (registration/<id>/<version>.json) answers. A hosted package's versions come from its own records and no upstream is asked (503 when those records cannot be listed). A registration leaf takes its listing from the registration NORA stored, so an unlisted version stays unlisted, and its upstream request carries the configured proxy credential.
  • pnpm and yarn install through NORA via corepack (#1225) — a version manifest (<name>/latest, <name>/<version>) asked for with Accept: application/vnd.npm.install-v1+json was answered as an abbreviated packument, {"name":…,"versions":{}}, and corepack failed with "Cannot destructure property 'tarball' of 'versionMetadata.dist'". As on registry.npmjs.org, only a packument is abbreviated now; manifests and dist-tags go out whole whatever the Accept.
  • With docker_anon_pull on, a push with credentials works (#1226) — NORA answered the /v2/ ping 200, so docker never sent the credentials docker login stored: a login with any password succeeded and a push failed with unauthorized. With docker_anon_pull on, the ping now answers 401 with a Bearer challenge naming /api/docker/token, as Docker Hub does: a client without credentials gets a token that pulls, one with credentials (Basic from docker, skopeo and podman, the password form from containerd) a token carrying its user and role, and a wrong password is a 401 that counts toward the lockout. A token lives 300 s and is honoured on /v2 paths only; its key is kept in token_storage/docker-token.key, so replicas sharing that directory share it. A token issued for an API token sent as the password ends when that API token is revoked or expires. POST /api/docker/token accepts a body of at most 64 KiB (413 above), and containerd's retry of a refused password, from the same address within 30 s, is not counted a second time. Without docker_anon_pull nothing changes.
  • NuGet search no longer stops restore, says when it is unavailable, and finds imported packages (#1233) — search and autocomplete are proxied to their own hosts (nuget.search_service, nuget.autocomplete), yet they reported to the one nuget circuit breaker, so a failing search host opened it and restore of a package not cached yet got 503 while the package source was healthy; each search host now has a breaker of its own, nuget:<url>, with its nora_circuit_breaker_state series exported from start, and the package source keeps nuget. With the search host unavailable, search answered 200 with whatever the local index held, an empty page included, which a client reads as "no such package"; the local index now answers, marked stale, only when the page asked for has entries, and otherwise search and autocomplete answer 503 (with Retry-After when the breaker is open). A package brought in by nora import was not found by search although restore installed it, and an id an upstream had served before showed the upstream's versions; search and autocomplete now list NORA's own packages with the versions NORA holds, ahead of the search host's results and in place of the host's entry for the same id, keeping to skip and take. When NORA's own packages cannot be listed, search answers 503 rather than the host's view of them. Pages merged from a live search host hold to skip and take without gaps where the host lists an id NORA does not show, totalHits is exact for results of up to 100 entries and never below what the pages hold above that, a page deeper than NORA reads the host for is a 503, and take is held to 1000, as nuget.org holds it. Autocomplete through a live host lists NORA's own ids first and no id in an internal namespace. A registration leaf whose stored registration cannot be read is a 503, not a 404.

Security

  • Curation and namespace isolation are checked under the names a proxied request is sent by (#1150) — on a cache miss in proxy mode, a package name or version could hold a byte that curation saw but the upstream request did not carry (a control character, or ? or #, which end a URL path), so the upstream could be asked for a different name than the one blocklist rules and internal_namespaces were checked against: a refused package could be fetched and cached, and an internal name could reach a public upstream together with the configured upstream credential. This applied to Terraform provider downloads and to the proxy paths of Go, Maven, npm, Cargo (the version), PyPI, NuGet, CPAN and Hugging Face; the Debian and RPM proxies, which no curation rule covers, could fetch another file and cache it under the name asked for. Each format now checks its names and versions against the characters the format allows before curation, storage or the upstream sees them, and answers 400 otherwise; a Terraform provider file is fetched only from the address, and under the file name, that the upstream's download metadata gives. The Debian and RPM proxies check their paths the same way. Storage keys refuse control characters, and a PyPI upload or Maven deploy under such a name is refused instead of stored where reads do not reach it; ? and # stay plain bytes where no upstream URL is built from a key (raw files). Names legitimate in each format keep working, measured against each client's own rules (@ in CPAN files, ~ in Maven and ^ in RPM versions, = in Go versions). Cached files that went through the checks before, and hosted repositories, were not affected. After upgrading, review proxied files in storage for names you do not expect.
  • rustix 1.1.6 (RUSTSEC-2026-0486, #1231) — rustix 1.1.4's xattr functions marked unwritten bytes as initialized when given a zero-length buffer. NORA's own code uses rustix for file locks only; the update keeps the dependency audit clean, and no Linux build input changes.
  • quinn-udp 0.5.16 (RUSTSEC-2026-0538, #1236) — quinn-udp 0.5.15's receive loop could spin after a truncated datagram. It is not built into NORA (an optional dependency of reqwest that NORA does not enable); the update keeps the dependency audit clean, and no Linux build input changes.

Install

# x86_64
curl -LO https://github.com/getnora-io/nora/releases/download/v1.4.5/nora-linux-amd64
chmod +x nora-linux-amd64
sudo mv nora-linux-amd64 /usr/local/bin/nora

# ARM64 (Apple Silicon, Graviton, Ampere)
curl -LO https://github.com/getnora-io/nora/releases/download/v1.4.5/nora-linux-arm64
chmod +x nora-linux-arm64
sudo mv nora-linux-arm64 /usr/local/bin/nora

Docker

docker pull getnora/nora:1.4.5
Variant Image Platforms
Alpine (default) getnora/nora:1.4.5 amd64, arm64
RED OS getnora/nora:1.4.5-redos amd64
Astra Linux SE getnora/nora:1.4.5-astra amd64
GHCR ghcr.io/getnora-io/nora:1.4.5 amd64, arm64

DEB / RPM

# Debian / Ubuntu / Astra Linux (amd64)
curl -LO https://github.com/getnora-io/nora/releases/download/v1.4.5/nora-amd64.deb
sudo dpkg -i nora-amd64.deb

# RHEL / Fedora / RED OS (amd64)
curl -LO https://github.com/getnora-io/nora/releases/download/v1.4.5/nora-amd64.rpm
sudo rpm -i nora-amd64.rpm

Changelog

See CHANGELOG.md

Don't miss a new nora release

NewReleases is sending notifications on new releases.