finds.dev

shlee322/delivery-tracker

🚚 Delivery and Shipping Tracking Service

View on GitHubHomepage ↗

★ 674TypeScriptNOASSERTIONupdated Feb 2026

// the take

A TypeScript monorepo that scrapes carrier tracking pages and exposes a unified GraphQL API. Heavy on Korean carriers (20+ kr.* packages), with a handful of international ones (DHL, FedEx, UPS, USPS, TNT, Cainiao). Self-hostable via Docker or usable as a managed cloud service at tracker.delivery.

1. The carrier namespace convention (country.carrier.variant) is clean and makes the registry easy to extend without collision. 2. GraphQL as the interface layer is the right call here — cursor-based pagination for event streams, typed schemas, one endpoint regardless of carrier. 3. The split between packages/core (scraping logic) and packages/api (query layer) means you can embed the core in your own app without pulling in the HTTP server. 4. Codespaces one-click setup actually works for a project like this, where local carrier credentials are usually the blocker.

1. The README is nearly empty — no documentation on what the GraphQL schema looks like, no example queries, just a link to an external docs site that may or may not stay up. 2. Carrier coverage drops off hard outside Korea; US coverage is FedEx/UPS/USPS only with no regional carriers, and Europe is just DHL and TNT. If your packages ship through LaserShip or OnTrac, you're on your own. 3. All carrier implementations are scrapers, not API integrations — which means any carrier site redesign silently breaks tracking with no alerting mechanism in the codebase. 4. No rate limiting or caching layer visible in the source; hammering carrier sites directly per request will get your IP blocked fast in production.

We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
674
Forks
214
Language
TypeScript
License
NOASSERTION
Last commit
12 Feb 2026

// nearby

If delivery-tracker isn't quite it.

All repos →