Each one solves a problem we know from building software: uploads lost when the signal drops, a CDN whose official Node.js client had no types, financial ratios that go wrong without an error. Each is published under the MIT licence with tests, documentation and a changelog.
Every package has its own documentation site, public CI, a changelog and a page here that says why it exists.
0.5.8 · released 29 Oct 2026 · MIT
A persistent task queue for Dart and Flutter. Uploads, messages and syncs are saved before they run, retried with backoff and recovered after a crash, and uploads can finish after the app is closed.
Solves: a retry loop in memory dies with the app, and the upload dies with it.
flutter pub add durable_queue1.1.1 · released 29 Oct 2026 · MIT
A typed, promise-based client and command line tool for the Akamai NetStorage HTTP API: upload and download files or buffers, list, inspect and manage files, with Akamai's method names.
Built because Akamai's own Node.js client for NetStorage has callbacks and no types.
npm install ts-netstorageapi-akamai1.3.2 · released 29 Oct 2026 · MIT
Financial ratios and fundamental analysis for JavaScript and TypeScript: valuation multiples, Piotroski F-Score, Altman Z, DCF and intrinsic value, with plain-English ratings and zero dependencies.
Solves: ratio formulas that go wrong without an error, such as a growth unit off by 100 or a NaN on a chart.
npm install fundamental-analysisThe bar we hold client code to, applied in public where anyone can check it.
All three run their tests in public CI on pushes and pull requests, and durable_queue also kills its demo app on an Android emulator and an iOS simulator.
Each package has its own site with a guide, an API reference and examples, plus a live playground or demo where it helps.
durable_queue's core and fundamental-analysis have no runtime dependencies. The Akamai client has two.
Semantic versions and a changelog that lists changes in behaviour before you upgrade.
An agency publishing open source is not a charity project. Code that anyone can read, install and test is the most direct proof of how we work: how we structure a library, what we test, how we document, and what we promise and refuse to promise.
It also keeps us honest. A client sees our work after delivery; a package is reviewed by every developer who installs it.
Yes. Every package is MIT licensed: free to use, change and ship in commercial and closed-source products.
Not answered here?
Tell us what you are building. We will show you how we would build it, and you see the work before you pay.