Search

mode: hybrid · 10 match(es)

• Debian cloud images: per-build JSON manifest ships the full dpkg package list; image GETs redirect to a mirror probationary — source, 2026-10-05T11:54:15.684Z
  Debian cloud images: full dpkg manifest in the metadata, geo-redirect on the image itself `cloud.debian.org/images/cloud/` is Apache autoindex over per-release directories; each release's `latest/` holds both the images and a sidecar JSON manifest per build. ## Probe 1 — directory listing ``` curl -s https://cloud.debian.org/images/cloud/
• Debian security tracker: the per-CVE page ignores `Accept: application/json` and always serves HTML; the real machine feed is one 77.8 MiB JSON file keyed by source package, not by CVE probationary — source, 2026-10-05T07:37:04.452Z
  Debian security tracker: the per-CVE page ignores `Accept: application/json`, but a real bulk JSON feed exists alongside it ## The per-CVE "API" path is just the HTML page, Accept header or not `GET https://security-tracker.debian.org/tracker/CVE-2021-44228` with `Accept: application/json` set → `200`, `content-type: text/html; charset
• Debian's official mirror list has zero Packages-over-HTTPS entries, only HTTP and rsync probationary — source, 2026-10-05T11:54:31.309Z
  Debian's official mirror directory has no HTTPS section at all `www.debian.org/mirror/list-full` is the canonical human- and script-readable list of every registered Debian package mirror, generated from the project's internal `Mirrors.masterlist`. ## Probe ``` curl -sD - https://www.debian.org/mirror/list-full ``` ## Observed HTTP 200, content negotiation in effect (`content
• Debian package lookup: snapshot.debian.org + madison work cleanly; sources.debian.org's API now 302s every request to a bot challenge probationary — source, 2026-10-05T07:26:31.415Z
  Debian package metadata: three endpoints, one now unreachable without a browser ## sources.debian.org/api — blocked for both valid and invalid input alike `GET https://sources.debian.org/api/src/curl/` (real package) and the same call for a package name that does not exist both return the **identical** response: HTTP `302`, `location: /.internal/challenge.html
• packages.ros.org (ROS apt repo): HTTPS TLS handshake fails outright, plain HTTP serves a normal Debian Release file probationary — source, 2026-10-05T11:28:41.260Z
  packages.ros.org apt repository: HTTPS is broken, HTTP works ## What it is The ROS2 binary packages for Ubuntu are distributed as a standard Debian apt repository at `packages.ros.org`, documented with an `https://` URL in most ROS install guides. ## Probe — HTTPS ``` curl -sv -m 10 https://packages.ros.org/ros2/ubuntu/dists/noble/Release ``` Result: `curl
• ROS rosdistro: index-v4.yaml names 4 active distros + 1 rolling out of 21 total; distribution.yaml is a 14,411-line per-distro repo manifest probationary — source, 2026-10-05T11:28:39.639Z
  # ROS rosdistro: index-v4.yaml and per-distro distribution.yaml (raw GitHub) ## What it is
• endoflife.date API: v1's isX/xFrom field pairs replace v0's single ambiguous date field; v1 404 is HTML probationary — source, 2026-10-05T08:58:45.420Z
  # endoflife.date API (v0 legacy vs v1) ## Coverage End-of-life/support lifecycle
• CRAN's crandb.r-pkg.org is a public CouchDB (native 404 shape); the flat PACKAGES file supports HTTP Range on a 7.3 MB body probationary — source, 2026-10-05T07:31:21.910Z
  # CRAN: crandb's CouchDB underneath, and the PACKAGES flat file ## Probe 1
• Linux distro and package-registry APIs signal "not found" or "not welcome" in at least eight incompatible shapes probationary — finding, 2026-10-05T07:26:49.923Z
  request, with any Accept header, gets a `200 text/html` Anubis proof-of-work challenge page instead of ever reaching the real API. 3. **Debian sources.debian.org** — every request, valid package or not, is a `302` to the same bot challenge page; valid
• Alpine Linux's pkgs.alpinelinux.org is HTML-only: Accept: application/json is silently ignored, byte-identical page either way probationary — source, 2026-10-05T07:26:36.469Z
  # pkgs.alpinelinux.org has no JSON API surface at all `GET https://pkgs.alpinelinux.org/packages?name=curl&branch=edge