Fake Candidates Checker
Pricing
from $0.02 / 1,000 results
Go to Apify Store
Fake Candidates Checker
The Fake-Candidates-Checker is intended to flag risky LinkedIn-profiles by: Verifying profile URLs resolve correctly before crawling. Collecting page titles and links as a baseline dataset. Cheerio-based crawl loop that you can extend to score red flags such as thin work histories, low connection
Pricing
from $0.02 / 1,000 results
Rating
0.0
(0)
Developer
christopher athans crow
Maintained by Community
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
Fake-Candidates-Checker
An Apify Actor for checking candidate authenticity. It validates provided candidate data, crawls linked evidence (profiles, resumes, employer verification URLs), and produces a scored verdict with anomalies and evidence links.
Project structure
.actor/actor.json— Actor configuration (name, version, runtime, metadata).actor/input_schema.json— Candidate-focused input (name, emails, phones, claimed employers, profile/resume URLs, crawler limits).actor/output_schema.json— Links to dataset view with verdicts.actor/dataset_schema.json— Output view definition for verdicts, anomalies, and evidencesrc/main.js— Actor entry point (Cheerio-based crawler with validation, scoring, and evidence aggregation)Dockerfile— Container definition for deployment
What it checks
- Candidate identity presence on provided pages (name match)
- Claimed employer mentions on provided/verifier URLs
- Email domains against employer domains (when provided)
- Phone number format sanity checks
- Aggregated evidence with per-URL status, title, and hits
- Simple scoring (0–100) and verdict buckets:
verified,needs_review,high_risk
Development workflow
- Install dependencies (skip if already installed in your environment):
$npm install
- Run the Actor locally:
$apify run
- Authenticate with Apify (once per environment):
$apify login
- Deploy to the Apify platform:
$apify push
Notes
- Uses CheerioCrawler (no Playwright) for speed; add Playwright only if you need JS rendering.
- Respect robots.txt and site ToS; provide only URLs you are permitted to fetch.
- The
storage/directory is ignored locally and created automatically by Apify during runs.
