Every source that goes through the Source Indexing Policy gets an entry here: what was proposed, who proposed it, which rules were checked, and how they were verified. The point is that a stranger can reconstruct any decision from the outside without asking anyone.
Two things this log deliberately is not: a ranking, and a promise. Rule 4 says it plainly — indexing is not endorsement, and distribution is not owed.
How to read an entry. "Verified" means someone ran a command and reported the output, not that a claim was accepted. Where a check could only be done against a live endpoint, the entry says what was sampled and when, because live checks expire: a source that passed in August can drift in November, and re-verification is normal rather than an accusation.
Adding an entry. A source is logged when its provider merges. Anyone can open a source proposal; the discussion happens in the issue and the PR, and this file is the durable summary with links back to both.
| Proposed by | @eliador90, who operates the source (declared in the proposal) |
| Provider | providers/remotli.mjs |
| PR | #2465 · issue #2464 |
| Merged | 2026-08-07 |
| Status | Listed |
First source reviewed under the written policy. The operator proposing their own board is exactly the case the rules exist for: the disclosure came first, and the rules decided rather than a conversation.
Rule 1 (real listings, identifiable employer, free for candidates). Verified: listings resolve to named employers, no candidate-side paywall or registration on the source.
Rule 2 (canonical URL is the employer's). The provider prefers each listing's upstream applyUrl and falls back to the board page only when that is missing or not https:. Verified by sampling 121 rows across pages 1, 9 and 19 of the live feed: zero rows without an employer URL, zero non-https, zero pointing back at remotli.ch. The host distribution was ordinary employer infrastructure (Greenhouse, Workday, Ashby, Lever, Recruitee, company career pages), with no tracking hop in between.
Rule 3 (complete inventory, no paid placement). The operator disclosed a coverage gap in his own proposal: without the remote=all parameter the feed serves 392 of 921 roles, 42.6% of the board. The merged provider walks all 19 pages. No promoted or sponsored field exists in the payload.
Rule 4 (operator declared). The supported boards table row carries operator: eliador90 with a link to this policy.
Rule 5 (aggregation stays in core). The provider reads its own source only. Ranking and cross-source work stay where they always were.
Also checked, outside the policy: zero-auth (a plain curl with no key, cookie or session returns the feed), and two HIGH CodeQL alerts raised in review were resolved before merge.
| Proposed by | @justma16ze (community contributor, not affiliated with the source) |
| Provider | providers/a16z-speedrun.mjs |
| PR | #2231 |
| Merged | 2026-07-29 |
| Status | Listed |
Merged before the policy was written, and logged here because it is the case that prompted writing it: a large, well-connected talent network is exactly where "does indexing imply endorsement?" stops being theoretical.
Rule 3, retroactively. Two coverage defects were found and fixed after listing, both by contributors reading the live feed rather than the code: the page size was set to 100 while the feed serves 50, so the fetch stopped silently after one page (#2419), and a single transient upstream failure aborted the whole board fetch (#2506). Both are the failure mode rule 3 targets: partial coverage that reads as complete.
Rule 4. Listed with its operator declared. Rule 4's 40% ceiling exists so no single source, however large, dominates the registry.
| Proposed by | @d-ulker (registration issue #1697); plugin published by @uelkerd |
| Plugin | career-ops-plugin-theirstack (community plugin, provider hook, THEIRSTACK_API_KEY) |
| Listed | 2026-07-07, before this policy existed (2026-08-04) |
| Retired | 2026-09-05 |
| Status | Not listed. The plugin remains published in its own repository; the registry is only what the project lists. |
Re-read against the written policy after a second source of the same shape asked to be listed (JobsPipe, #3841), so that the two answers match.
Rule 1 (real listings, identifiable employer, free for candidates). Not met as a listed source: access to the listings goes through a metered, paid API on the job seeker's side, and a free tier does not change that. Manifesto right 4 ("You never pay") applied to sources is the whole of this rule; it has no free-tier exception.
Rule 5 (aggregation belongs to the project). The value of the source is a cross-source feed ("50k+ sources"), which is the layer the policy keeps in core.
Rules 2, 3 and 4. Not re-verified: rule 1 decides on its own. Rule 4 is worth restating for the record: indexing is not endorsement, and retiring a listing is not a judgement on the product.
| Proposed by | @nikitacometa, who operates none of the channels measured |
| Provider | providers/telegram-channel.mjs |
| PR | #3668 · issue #3701 |
| Merged | 2026-09-05 |
| Status | Provider listed; no channel is listed. The shipped job_boards: entry is a disabled template, and a channel added to the registry gets its operator declared per channel. |
First source of a new kind: not a board with a feed, but a transport (Telegram) carrying channels whose posts are written by hand. A board guarantees rules 1 and 2 by construction; a channel only satisfies them post by post, so the provider was asked to measure before it was read, and the measurement became its contract.
What was measured. 17 channels with a public preview (10 RU/CIS, 7 EN), 809 posts, up to 3 pages each, on 2026-09-03, with every surviving link opened by hand (137 links).
| RU/CIS (461 job posts, 77 CV posts) | EN (271 posts) | |
|---|---|---|
post names an employer (Компания: / Company: line, Title @ Employer, Title | Employer, a second line в Employer —) |
45% | 4% |
| post links outside Telegram and the vk/max footers | 70% | 74% |
| both, after dropping homepages, forms, shorteners, LinkedIn posts, pages with no vacancy evidence, hidden employers and multi-vacancy digests | 25% (137 posts) | 0 |
The pass rate is each channel's editorial shape, not noise: @data_science_job 77% (every post is Title [Remote] @ Employer plus a getmatch page), @ai_rabota 42%, @jobforjunior 42%, @job_python 35%, @backend_job_geeklink 32%; @devjobs 2%, @datasciencejobs, @theyseeku and @itjobs_ru 0% (a recruiter named instead of an employer, or an employer named with nothing linked). The EN channels in the sample mirror boards the project already scans (remoteok, weworkremotely, arbeitnow) or link only through shorteners, so they pass 0 and lose nothing.
Rule 1 (real listings, identifiable employer, free for candidates). The provider enforces employer-name and qualifying vacancy-link checks. company is that employer, never the channel and never the link's hostname; the 77 CV posts and every post naming a recruiter, an agency client or "название скрыто" are dropped. Manual review found no candidate-side paywall on the 137 sampled links. Free candidate access is an observation from that sample, not a runtime check or a guarantee for later posts.
Rule 2 (canonical URL is the employer's). url is the vacancy link the post carries: a vacancy page on the employer's own https host first, then a known board's per-vacancy page (getmatch.ru, finder.work, geekjob.ru, geeklink.io, hh.ru, linkedin.com/jobs/view). Rejected: t.me, social and footer hosts, shorteners, forms, homepages and listing roots, employer pages with no vacancy evidence, plain http. Of the 137 emitted links, 53 are employer vacancy pages and 84 board per-vacancy pages. The t.me permalink is secondary attribution only, carried as a trailing Source: line; a post with no external vacancy link is not emitted at all.
Rule 3 (complete inventory, no paid placement). The provider pages the public t.me/s/ preview newest first through the since_days window; max_pages is a safety cap that warns when it cuts the window short. Accepted posts retain their HTML order within each preview page; pages are fetched from newest to older, without globally sorting the emitted jobs. Whether an operator sells posts to employers is not visible in provider data and remains unverified. A paid post can pass the same employer-and-vacancy-link checks as any other post, so those checks do not establish the absence of paid promotion.
Rule 4 (operator declared). Per channel, not per transport: the registry names the channel, and the shipped example is disabled. Indexing a channel is not endorsement of its operator.
Rule 5 (aggregation stays in core). The provider reads one channel per entry and does no cross-source work. The one change outside the provider, aggregator: true in scan.mjs, only switches off cross-employer title dedup for a feed that names itself as the company; dedup, ranking and matching stay where they were.
The bar for the next channel proposal, so it is written down: measure the channel (share of posts naming an employer, share linking a vacancy page, what survives both), name its operator, and expect the provider to drop the rest. A channel below roughly a quarter passing is the channel's editorial choice, and the provider will read it correctly and emit little.
| Proposed by | @configurowebmax (community contributor; no affiliation with the source declared) |
| Provider | providers/computrabajo.mjs |
| PR | #2650 |
| Merged | pending (this PR) |
| Status | Provider listed; the shipped job_boards: entry is enabled: false. |
A general job board with one host per Latin American country. Only the Colombian host was measured: one GET of https://co.computrabajo.com/trabajo-de-sistemas on 2026-10-23, no key, cookie or session, career-ops' default User-Agent: HTTP 200, 20 posting cards.
Rule 1 (real listings, identifiable employer, free for candidates). Employer attribution, measured: 17 of the 20 cards name an employer; 3 show "Importante empresa del sector" (hidden employer), which the provider emits as ?. Several named employers are staffing agencies rather than the hiring company. Free for candidates: met. Creating an account and applying cost nothing ("Registro gratuito" on co.computrabajo.com, read 2026-10-23); applying goes through a free candidate sign-in. Computrabajo also sells candidates an optional "Cuenta Premium" (co.computrabajo.com/cuenta-premium/, about COP 12,000 a month on 2026-10-23) that, among other things, puts the profile in the first positions employers see and allows applying more than once to the same vacancy. Applying does not require it. career-ops does not use, link to or recommend that plan: the provider only reads public listings and links each posting page.
Rule 2 (canonical URL is the employer's). The listing card carries no employer or ATS URL, only the board's own posting page, so url is that page (fragment dropped). Whether the posting page links on to the employer: unverified.
Rule 3 (complete inventory, no paid placement). Partly met, flagged for the maintainer. Employers can pay Computrabajo (not career-ops) to feature a posting as "Empleo destacado", and the board interleaves those cards in every sort order: 9 of 20 in the default "Relevancia" order and 11 of 20 in the "Fecha" order (?by=publicationtime), measured on 2026-10-23. There is no order without them, and they are real postings by real employers, so the provider keeps them. It requests the "Fecha" order so the newest postings come first, keeps every card it reads, does no ranking of its own, and stops at 3 pages / 15 postings by design. career-ops receives nothing from Computrabajo or from any employer. Pagination (?p=N) is unverified.
Rule 4 (operator declared). Operator not declared in the PR; unverified.
Rule 5 (aggregation stays in core). Verified in code: the provider reads one search URL per entry, on a <country>.computrabajo.com host only.
Rule 6 (robots.txt). Checked on 2026-10-23: one GET of https://co.computrabajo.com/robots.txt with career-ops' default User-Agent, HTTP 200, a single User-agent: * group. Its Disallow lines cover /ofertas-de-trabajo/ with filter parameters (*by=, *pubdate=, ...), /hojas-de-vida/, /curriculums/, /empresas/ filters, /Ajax/, /_services/ and /go/; none covers the search page the provider fetches (/trabajo-de-sistemas?by=publicationtime&p=N). A configured search URL under /ofertas-de-trabajo/ would fall under the *by= rule once the provider adds by=publicationtime; the shipped entry's path is not under it. Other country hosts: unverified.
Proposed in #2650 together with Computrabajo and Magneto365, and taken out of it on 2026-10-23. The comments in https://www.elempleo.com/robots.txt (read 2026-10-23) say that extracting or scraping its content by automated means is prohibited without ELEMPLEO's prior written permission. A provider reads the board by automated means, so it is not listed. The provider code stays in the history of #2650 (providers/elempleo.mjs at e40e148) in case ELEMPLEO gives that permission.
| Proposed by | @configurowebmax (community contributor; no affiliation with the source declared) |
| Provider | providers/magneto.mjs |
| PR | #2650 |
| Merged | pending (this PR) |
| Status | Provider listed; the shipped job_boards: entry is enabled: false. |
A general job board for Colombia. Measured: one GET of https://www.magneto365.com/co/trabajos/buscar/tecnologia on 2026-10-23, no key, cookie or session, career-ops' default User-Agent: HTTP 200, 20 job cards, pager links up to page 20.
Rule 1 (real listings, identifiable employer, free for candidates). Employer attribution, measured: 11 of the 20 cards name an employer; 5 read "Confidencial" and 4 carry the board's own name ("Magneto empleos"), and the provider emits all 9 as ?. Free for candidates: met according to the press, not to a Magneto page: candidates register, upload a CV and apply at no cost, and employers pay for credits to see candidate contacts (El Colombiano, read 2026-10-23). Applying requires a free account.
Rule 2 (canonical URL is the employer's). The card carries no employer or ATS URL, only the board's own posting page, so url is that page. Whether the posting page links on to the employer: unverified.
Rule 3 (complete inventory, no paid placement). The default sort order and whether any card is promoted: unverified. The provider reads up to max_pages (default 5), not the whole board. The pagination shape (?paginator[page]=N) is the one in the page's own pager links; a page past the first was not fetched.
Rule 4 (operator declared). Operator not declared in the PR; unverified.
Rule 5 (aggregation stays in core). Verified in code: the provider reads one search URL per entry, on www.magneto365.com / magneto365.com only.
Rule 6 (robots.txt). Checked on 2026-10-23: one GET of https://www.magneto365.com/robots.txt with career-ops' default User-Agent, HTTP 200. Under User-agent: * it allows /, disallows /*? and /manager/*, and allows /*paginator[page]. Every URL the provider fetches carries paginator[page]=N, which the longer Allow covers; a configured search URL with other query parameters still carries it. No group names career-ops.
| Proposed by | @kosinal (not the operator) |
| Provider | providers/jobscz.mjs, providers/pracecz.mjs |
| PR | #5631 · issue #5627 |
| Merged | — |
| Status | Proposed |
Rule 1 (real listings, identifiable employer, free for candidates). Listings are individual offers, and each names its employer: a company line on every jobs.cz card, company.publicName on every prace.cz item. Listings are readable without an account, and the prace.cz footer links an advertising price list for employers ("Ceník inzerce"). Each offer page has an "Odpovědět" (reply) button leading to the portal's application form. It was opened by hand in a browser, as a candidate, on one offer of each portal (the providers never request it; prace.cz's robots.txt disallows /odpovedni-formular/): on both portals, sending an application requires no account and is free.
Rule 2 (canonical URL is the employer's). jobs.cz cards link https://www.jobs.cz/rpd/{id}/, which redirects to the offer page, often on the employer's branded career site ({employer}.jobs.cz/pd/{id}). The listing exposes no direct ATS link, so /rpd/{id}/ (without tracking params) is the canonical URL. On prace.cz, an item's extended.careerPage.url, the employer's branded page, is used when present; otherwise https://www.prace.cz/nabidka/{advertId}/.
Rule 3 (complete inventory, no paid placement). Both portals mark promoted placement: "Příležitost dne" cards (data-test-ad-status="jobsTip") on jobs.cz, searchInfo.isPromoted on prace.cz. Neither portal has a sort control. Walking every page of a search returns exactly the total the site shows: for "python", jobs.cz returned 281 unique offers over 10 pages, and prace.cz 63 over 2 pages. The providers walk all pages up to a cap, warn when the cap is hit, dedup by offer id, and leave ranking local. The id is the one in the offer URL on jobs.cz (/rpd/{id}/) and advertId on prace.cz, so an offer seen under both its branded career-page URL and /nabidka/{advertId}/ is kept once.
Rule 4 (operator declared). Alma Career Czechia s.r.o. runs both portals, according to their page footers. The proposer is not the operator, but a candidate using them.
Rule 5 (aggregation stays in core). Each portal has its own provider. jobs.cz and prace.cz are separate portals, but many employers publish the same offer on both: for "python", 56 of the 63 prace.cz offers also appeared on jobs.cz with identical company and title. The scanner's existing company+role dedup merges these.
Rule 6 (the source's own robots.txt). Under User-agent: *, jobs.cz does not disallow the listing path /prace/, and its disallowed /api/ and /iapi/ are never requested. prace.cz does not disallow /nabidky/, the only path the providers read; its disallowed /hledat/ (the old search path, which now redirects to /nabidky/) and application-form paths are never requested. Neither file names an AI or agent crawler.