How tabishassan/rung-check works
Rung Check is a LinkedIn profile scoring tool: a visitor uses the static site to request an audit and view a report, while the Cloudflare Worker proxies scoring-model requests and handles report email and lead logging. The Worker also contains a leads dashboard with analytics. The excerpts show the Worker’s external service calls and persistence, but omit much of its routing and scoring logic; the site source was not sampled, so its connection to the API is shown as unverified.
Main entry points: worker.js API Worker · index.html Static site
Components 13
Visitor experience
- Static site
site/public/index.html
Profile audit
- API Worker
api/src/worker.js - Profile scoring
api/src/worker.js - Groq API
- Audit report
api/src/worker.js
Lead operations
- Report email
api/src/worker.js - Brevo email service
- Lead logging
api/src/worker.js - D1 leads database
- Notion
Analytics
- Leads dashboard
api/src/worker.js - PostHog
Other components
- Visitor
Connections 11
- Visitor → Static site: uses
README.md - Static site → API Worker: requests audit
- API Worker → Profile scoring: routes audit
api/src/worker.js - Profile scoring → Groq API: requests completions
api/src/worker.js - API Worker → Report email: handles send-report
api/src/worker.js - Report email → Brevo email service: sends email
api/src/worker.js - API Worker → Lead logging: logs leads
api/src/worker.js - Lead logging → D1 leads database: inserts leads
api/src/worker.js - Lead logging → Notion: syncs optionally
api/src/worker.js - Leads dashboard → D1 leads database: reads leads
api/src/worker.js - Leads dashboard → PostHog: queries events
api/src/worker.js