Eric Yen/Products/Ghost Job Detector

⏸ Development paused from October 2026.

104's member terms (revised September 2026) restrict the use of unofficial automation tools, and restrict using the platform's content to build derivative services. So that no one's 104 account gets into trouble because of this extension, I've decided to pause development and stop offering downloads.

If you have it installed, I recommend removing it. Open chrome://extensions/, find "幽靈職缺偵測器" (Ghost Job Detector) and click "Remove".

The source code stays on GitHub under the MIT license. Thank you to everyone who used it and reported problems.

Ghost Job Detector

No reply to your application doesn't mean you weren't good enough. Maybe nobody was reading.

A Chrome extension for 104, Taiwan's largest job board. On every listing, it prints the half of the data 104 has but never shows.

FreeOpen sourceCollects no dataDevelopment pausedLast version v1.8.0

Built independently. Not an official 104 product.

Below is the page as it was before development paused (last version v1.8.0), kept for the record. The extension is no longer available for download; what follows describes how it behaved then.

01 · The problem

104 only shows you the good half

104 knows how many days ago each listing last processed a résumé and last replied to an applicant, and it already sends those fields to your browser when a listing loads. But the page only shows the good half: "processed résumés within 3 days" appears, while "no reply to any applicant in 30 days" disappears entirely. Applicant counts too: you get a band like "6–10", never the exact number.

This extension fills in the other half, then stays quiet: no scores, no grades, no guessing whether a job is real.

02 · What it shows

One extra row on every job card

FieldMeaningDoes 104 show it?
Résumés processedDays since HR last opened a résuméOnly when there is a record; otherwise the line disappears
Replies to applicantsDays since the company last replied through 104Same as above
ApplicantsThe exact count, or the band if unavailableOnly a band (0–5 / 6–10 / 11–30 / 30+)
PostedThe date, plus how many days agoOnly the date
RepostedHow many times the extension has seen this listing repostedNot at all
Open rolesHow many roles the company has openOn the company page, not the listing

Just three visual cues, none of them a grade:

✓ Green

Résumés processed or replies within 7 days. Good news: HR is actually active.

Red

Posted more than 60 days ago. Worth a second look, not "this job is fake".

Bold on grey

Posted within 60 days. Only meaningful once turned into a day count.

03 · Why no score

Flagging a real job as fake hurts job seekers and companies alike

Early versions had a 0–100 score and four grades, since removed entirely. A sample of 1,039 unique listings on 2026-09-05 showed the premises didn't hold: "the longer it's up, the more abandoned it is" is false. Older listings actually had more active HR.

PostedListingsHR active within 7 daysNo activity in 30 days
> 30 days89(8.6%)93.3%0
> 60 days39(3.8%)89.7%0
> 90 days15(1.4%)86.7%0
> 180 days3(0.3%)100%0

Thresholds set by gut feeling can't get this right, so it now shows only the data and leaves the judgement to you. 完整分析 →

04 · How to remove it

If you have it installed, remove it

  1. Open the extensions page

    Type chrome://extensions/ into Chrome's address bar and press Enter. In Edge, Brave and others, use their own extensions page (for example edge://extensions/).

  2. Find "幽靈職缺偵測器" and click "Remove"

    Chrome asks once more; confirm. The data the extension kept on your computer (cache, listing history, hide rules) is deleted with it; nothing else to clean up.

    The extension card on the extensions page, with the Remove button at the bottom left
  3. (Optional) Delete the unzipped folder

    The folder you unzipped when installing it manually isn't needed once the extension is removed; you can delete it.

05 · Thank you

Thank you to everyone who used it and reported problems.

The source code stays on GitHub under the MIT license; the full "why no scores" analysis and implementation notes are in the README (in Chinese).