Thinwrap v1.0: direct-HTTP wrappers for the APIs you already use

June 4, 2026 · 1 min read

#launch #supply-chain #announcement

Thinwrap v1.0 is here — our first public release, live on npm and Packagist today. Four packages, two scopes, two languages, no vendor SDKs:

Notifications (email, SMS, push, chat) — @thinwrap/notifications · thinwrap/notifications
Location (routing, matrix, geocoding, isochrone) — @thinwrap/location · thinwrap/location

Each is a thin, direct-HTTP wrapper over 40+ providers you already use. One facade per category, and switching provider is a one-line change:

import { Routing } from '@thinwrap/location';
const google = new Routing('google', { apiKey: process.env.GOOGLE_KEY });
// same result shape, different provider:
const mapbox = new Routing('mapbox', { accessToken: process.env.MAPBOX_TOKEN });

Why

We started Thinwrap in February 2026 — thin, direct-HTTP wrappers, because vendor SDKs that only needed to hit one documented endpoint were dragging in an HTTP client and its whole transitive dependency graph. The axios compromise that March made the dependency surface the whole point: by April we’d stripped the TypeScript packages to zero runtime dependencies (hand-rolling the last bits, like AWS SigV4). The PHP packages stay on the standard PSR-18/17 HTTP interfaces plus php-http/discovery — no vendor SDKs either way.

Dropping the SDKs in production was striking enough to package up: 50 MB → 60 KB of dependency weight, and roughly 3 minutes off every CI run.

Get started

npm i @thinwrap/notifications          # or @thinwrap/location
composer require thinwrap/notifications  # or thinwrap/location

Find your provider in the catalog, read why we built it, or check the security posture. Run an API we wrap? Help co-maintain it.

That’s the release. Go build — and send feedback or a PR on GitHub.