nw-hiker-skier/quietsky-privacy-proxy — explained in plain English
Analysis updated 2026-05-18
Verify how a weather app's proxy strips IP addresses, headers, and cookies before contacting providers.
Study a real example of enforcing identity-stripping with automated source-scan tests.
Reference the SHA-256 manifest pattern for publishing verifiable hashes of withheld proprietary code.
Learn a cache-key design that rounds coordinates for sharing without exposing individual users.
| nw-hiker-skier/quietsky-privacy-proxy | 0xkinno/neuralvault | 0xmayurrr/ai-contractauditor | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | hard | easy |
| Complexity | 4/5 | 4/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
The core privacy logic is public, but the actual weather-provider adapters are proprietary and withheld from this release.
This repository is the privacy core of Quiet Sky, a weather app's proxy service, built as a Cloudflare Worker. Every request from the Quiet Sky Android app to a weather provider passes through this code, and its job is to strip out anything that could identify the person or device making the request, such as an IP address, device headers, cookies, or tokens, before the request continues on to the weather provider. The author is explicit that this repository exists so people can verify the privacy claims, not so they can reuse the whole system. The parts that handle identity stripping, cache key construction, logging, and rate limiting are all public and can be inspected. The actual code that talks to specific weather providers is kept private, and instead a SHA-256 hash file is published with each release so anyone can confirm the withheld code has not silently changed, even without seeing it. Two rules are enforced by the project's own automated test suite. First, only a small block of code near the top of the main file is ever allowed to read identifying information from an incoming request, and a test scans the rest of the code to make sure nothing else touches it. Second, every request sent onward to a weather provider is built completely from scratch in one place, so there is no way for inbound headers to accidentally get copied into an outgoing request. The proxy still sends location coordinates to providers, because a weather forecast needs to know where you are, but the precision of that location is controlled by a setting in the app itself. What gets removed is identity information, not location. Cached weather data is stored by rounded coordinates shared across nearby users, never tied to a specific person, and the project's logs only record aggregate counts and outcomes rather than anything that could identify a request or its sender. The project is licensed under Apache 2.0, which allows use, modification, and redistribution, including commercially, as long as the license terms and any required notices are preserved.
A Cloudflare Worker that strips identifying data from weather requests before they reach weather providers.
Mainly TypeScript. The stack also includes TypeScript, Cloudflare Workers.
Apache 2.0: free to use, modify, and redistribute, including commercially, as long as license terms and notices are preserved.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.