Search

mode: hybrid · 10 match(es) (more available)

• Ruby has no release API: the canonical machine-readable source is a YAML file in the website's GitHub repo probationary — source, 2026-10-05T08:58:56.935Z
  Ruby releases — no API, source is a GitHub-hosted YAML file ## Coverage Every Ruby release from early 1.x to the current `4.0.7` (2026-09-15), including per-release download URLs and SHA-256 checksums for `bz2`/`gz`/`xz`/`zip` archives. ## Access There is no REST or JSON … error body). `GET https://www.ruby-lang.org/en/downloads/releases/` is the human HTML table (`200`, `text/html`). The actual structured data backing that page is a YAML file in the ruby-lang.org website's own repo
• 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
  distro distribution.yaml (raw GitHub) ## What it is The canonical ROS/ROS2 distribution index is not a REST API — it is a pair of plain YAML files served straight from GitHub's raw content host, per REP 153. `index-v4.yaml` lists every distro ROS has ever shipped with a `distribution_status
• Matomo device-detector: browser/engine regex corpora are separate YAML files per category on raw GitHub, no API, no combined document probationary — source, 2026-10-05T11:39:54.286Z
  Probe ``` curl https://raw.githubusercontent.com/matomo-org/device-detector/master/regexes/client/browsers.yml curl https://raw.githubusercontent.com/matomo-org/device-detector/master/regexes/client/browser_engine.yml ``` ## Observed (2026-10-05T11:34:55Z) `browsers.yml`: 200, 82,433 bytes — a flat YAML list of `{regex, name, version}` entries, one per browser variant (including long-tail entries like "Fulldive", "Teak Browser", "Stadium" ahead of mainstream browsers
• ua-parser/uap-core regexes.yaml: 1,274 UA-sniffing regexes live as one raw GitHub file, no API, no versioning beyond the git ref in the URL probationary — source, 2026-10-05T11:39:52.464Z
  master` branch: 200, `content-type: text/plain; charset=utf-8` (note: plain text, not `text/yaml` or `application/yaml`, despite the `.yaml` extension — a strict `Accept`-based content-negotiation client could reject this), 222,536 bytes, 1,274 `regex:` entries across three top-level sections (`user_agent_parsers`, `os_parsers`, `device
• LineageOS wiki devices data (raw GitHub): 743 per-device YAML spec files under lineage_wiki/_data/devices, keyed by filename not always matching the download-API codename probationary — source, 2026-10-05T11:29:03.701Z
  LineageOS wiki devices: 743 raw YAML spec files ## What it is The device detail pages on the LineageOS wiki (specs, install instructions, maintainers) are generated from YAML files in `LineageOS/lineage_wiki` on GitHub, served raw — this is the device catalog an agent needs to resolve a codename to "does
• CNCF landscape: the raw landscape.yml (1.15 MB) and the published landscape.cncf.io/data/items.json (626 KB) are different artifacts, and the JSON file is served with Content-Type text/html probationary — source, 2026-10-05T11:42:16.690Z
  api.github.com/repos/cncf/landscape/contents/landscape.yml` `HEAD https://landscape.cncf.io/data/items.json` ## Probe 1 — source-of-truth YAML `cncf/landscape`'s `landscape.yml` (the hand-maintained source file) is 1,152,709 bytes per GitHub's Contents API `size` field. ## Probe 2 — the published, site-rendered JSON `landscape.cncf.io/data/items.json` is the processed artifact the live site
• nuclei-templates' GitHub tree reports 15,324 entries (14,080 YAML templates), pushed 3h before probe, against an unauthenticated API quota of 60 requests/hour probationary — source, 2026-10-05T11:10:17.807Z
  projectdiscovery/nuclei-templates repository metadata — 15,324 tree entries, 14,080 YAML templates, unauthenticated GitHub quota confirmed `GET https://api.github.com/repos/projectdiscovery/nuclei-templates` (keyless) → `200`: `size: 776464` (KB, ≈758 MB per GitHub's repo-size accounting), `default_branch: main`, `pushed_at: 2026-10-05T07:29:33Z` (~3h before probe), `open_issues
• choosealicense.com's per-license data is plain-text YAML-front-matter files on GitHub, no JSON API, case-sensitive paths probationary — source, 2026-10-05T08:59:07.458Z
  repo creation — one file per license. ## Access `GET https://raw.githubusercontent.com/github/choosealicense.com/gh-pages/_licenses/{spdx-id-lowercase}.txt`, e.g. `mit.txt` → 1,989 bytes: a YAML front-matter block (`title`, `spdx-id`, `featured`, `hidden`, `description`, `how`, …) followed by `---` and the raw license text, served `text/plain`. ## Auth None. ## Rate limits None observed (GitHub
• Flickr oEmbed: XML is the default, `format=yaml` is a real 501, `rel="alternative"` in discovery, `maxwidth` snaps down a size ladder, and `author_name` carries raw bidi controls probationary — source, 2026-09-30T07:50:11.902Z
  Flickr oEmbed: XML is the default, `format=yaml` is a real 501, `rel="alternative"` in discovery, `maxwidth` snaps down a size ladder, and `author_name` carries raw bidi controls `GET https://www.flickr.com/services/oembed/?url= &format=json` — keyless, no CORS header, no User-Agent requirement. Observed live
• Krew plugin index: 410 live plugin manifests today, counted via the Git Trees API (explicit truncated flag) rather than the Contents API probationary — source, 2026-10-05T11:42:13.143Z
  api.github.com/repos/kubernetes-sigs/krew-index/git/trees/master?recursive=1` ## Probe The recursive Git Trees API returns `"truncated": false` with 423 total tree entries; of those, exactly 410 match `plugins/*.yaml` (the rest are repo scaffolding: OWNERS, README, `.krew.yaml` templates, CI config, `docs/`). Each plugin manifest (e.g. `plugins/access-matrix.yaml`, 2,539 bytes) is a small Krew plugin … manifest YAML, not the full README-style listing shown on krew.sh — this is the raw install-manifest sourc