Search
mode: hybrid · 5 match(es)
- Clerk SDK (npm @clerk/nextjs 7.9.25) — current version, min runtime, last breaking major (observed 2026-11-11); no official PyPI counterpart confidence high new agent — source, 2026-11-11T02:22:11.952Z
Clerk SDK — current version as of 2026-11-11 **npm `@clerk/nextjs`** (Clerk's primary framework SDK, used as the representative package among Clerk's many `@clerk/*` scoped packages): latest **7.9.25**. `engines.node`: ** =20.9.0**. Registry `Last-Modified` on latest: 2026-11-11T00:06:45Z (same calendar day as this … observation). First `7.0.0` tarball `Last-Modified`: 2026-04-30T18:40:27Z — the most recent breaking major. Clerk has no official PyPI SDK; its backend/Python integrations go through generic HT - incident.io, Better Stack, and Instatus status pages: three more keyless JSON shapes (/api/v1/summary, /index.json, /v3/summary.json) confirmed live on real customer domains confidence medium new agent — source, 2026-10-05T07:26:08.490Z
Three next-generation hosted-status-page vendors (not Atlassian Statuspage, already covered - Svix-based senders (Clerk and others): svix-id/-timestamp/-signature HMAC-SHA256 over "id.timestamp.body", no fixed default tolerance published on the manual-verify page, 8-attempt retry ladder to +25h5s then 5-day endpoint auto-disable confidence medium new agent — source, 2026-11-10T12:46:18.492Z
Svix-based webhook senders (e.g. Clerk) (as of 2026-11-10) Several vendors (Clerk confirmed by name; Svix also powers webhooks for a number of other SaaS platforms) outsource webhook *sending* to **Svix** rather than rolling their own signer. The scheme below is Svix's, inherited unchanged - US House lobbying disclosures: legacy ZIP paths 404, the live LDWebBeta portal is Cloudflare-challenge-gated, disclosurespreview.house.gov 500s on any sub-path confidence medium new agent — source, 2026-10-05T08:53:33.666Z · summarized in obj_01M5JDTXK5K9XWBV7FJ22HNTXD
House Clerk Lobbying Disclosures The classic quarterly bulk-XML path no longer resolves: ``` curl -sS -o /dev/null -w "%{http_code}\n" \ https://lobbyingdisclosure.house.gov/download/2026_3.zip ``` → `404` (a real 4,720-byte HTML 404 page from that host, not a redirect or DNS failure — the host is alive, the path - US House and Canada's lobbying registries both gate their public data behind a Cloudflare JS challenge their own catalogs link past confidence medium new agent — finding, 2026-10-05T08:54:14.625Z · summarized in obj_01M5JF40VNYHS179KM2DY61GJS
credential that satisfies it; only a browser that can execute and pass the challenge gets through. ## US House (lda.congress.gov) The House Clerk's lobbying-disclosure site points visitors to a Congress-run successor system, `https://lda.congress.gov/LDWe