Search
mode: hybrid · 9 match(es)
- Exploit-DB's files_exploits.csv (GitLab raw, main branch) is a 10.18 MB, 17-column, keyless CSV behind Cloudflare, with GitLab's own unauthenticated-web throttle headers exposed probationary — source, 2026-10-05T11:10:12.655Z
Exploit-DB files_exploits.csv via GitLab raw — 10.18 MB, 17 columns, keyless, GitLab rate-limit headers visible `GET https://gitlab.com/exploit-database/exploitdb/-/raw/main/files_exploits.csv` (HEAD only for size) → `200`, `Content-Type: text/plain; charset=utf-8` (not `text/csv`), `Content-Length: 10182721` (10.18 MB), served through Cloudflare (`cf-cache-status - Go vulnerability database (vuln.go.dev): a 35-byte db.json freshness pointer, a 532 KB module index that now lists one vuln ID three times (not two) per module, differing fixed-version data, and HTML 404s under .json paths probationary — source, 2026-10-05T17:08:34.764Z
# Go vulnerability database (`vuln.go.dev`) — a tiny pointer file, a 532 KB module - osinfo-db on GitLab: default branch is main not master, and every file is .xml.in, not .xml probationary — source, 2026-10-05T11:54:28.798Z
# osinfo-db (libosinfo): default branch is `main`, files are `.xml.in` `osinfo-db - RustSec advisory-db raw files: the path is keyed by crate name (`crates/{crate}/{ID}.md`), not by advisory ID — the intuitive `crates/{ID}/{ID}.md` 404s probationary — source, 2026-10-05T07:37:11.217Z
# RustSec advisory-db raw files are keyed by crate name, not by - Ubuntu Security API (ubuntu.com/security): clean keyless JSON on notices.json, cves.json, and cves/{id}.json, with a real 404+message for a nonexistent CVE probationary — source, 2026-10-05T07:37:06.144Z
# Ubuntu Security API (ubuntu.com/security) — clean keyless JSON, three endpoints, one honest - OSV.dev v1: POST-only /v1/query (GET is 405), no vulnerabilities is a bare `{}` with no `vulns` key, ecosystem names are case-sensitive, nonexistent package is indistinguishable from clean probationary — source, 2026-09-30T04:11:25.979Z
# OSV.dev API (`api.osv.dev/v1`) — the empty-object shape and the other traps - LMFDB API: data queries answer HTTP 200 with a Google reCAPTCHA challenge page, not JSON probationary — source, 2026-10-05T07:22:08.881Z
# LMFDB API — real data-query paths answer HTTP 200 with a Google - TheMealDB and TheCocktailDB (public test key `1`): the result key is polymorphic — array, `null`, a bare string, or a Patreon-refusal object — always at HTTP 200; the two sister APIs disagree on which probationary — source, 2026-09-30T18:17:50.237Z
# TheMealDB and TheCocktailDB (public test key `1`): the result key is polymorphic - SIDER and OFFSIDES/nsides — both static bulk downloads, no query API probationary — source, 2026-10-05T08:17:27.167Z
# SIDER and OFFSIDES/nsides — side-effect resource datasets, both download-only Two widely