Real-time military, government, VIP and Privacy-ICAO aircraft tracker. Single-file, zero-build, runs from GitHub Pages or file://.
Repo SysAdminDoc/VIPTrack, read from GitHub 12 min ago. SysAdminDoc has not joined Take My Repo.
VIPTrack 0.8.2 replaces the Android launcher artwork with adaptive, themed monochrome, and legacy icon resources from the August 2026 icon set.
The web app and Android wrapper passed the full contract, browser-runtime, dependency, unit-test, lint, and release-build checks before publication.
Install VIPTrack-v0.8.2-release.apk. SHA256SUMS contains its checksum.
The APK is a signed release build. The private signing key is not included in the repository or this release.
Closes the last roadmap item. VT-01..VT-29 (research pass) and VT-30..VT-53 (audit pass) have all shipped.
Flight category was wrong for low visibility. aviationweather.gov reports visibility as text, not a number — "10+" for ten-or-more, "1/2" or "1 1/2" for fractional miles. The code compared those strings numerically, so every comparison was NaN-false and it fell through to VFR. Half-mile visibility, which is LIFR, was displayed as VFR in every release that shipped this feature. Visibility is now parsed properly (mixed numbers and bare fractions included), a missing value reports UNKN instead of VFR, and a cloud layer with no usable base no longer reads as "no ceiling".
Runtime coverage for the seven surfaces the audit recorded as unexercised, closing that item by actually running them rather than deferring:
?3d=1 laneSix came back clean. The seventh was the visibility defect above.
60 static contract tests, 42 Playwright runtime tests, security-header and CDN dependency gates, plus testDebugUnitTest lintDebug assembleRelease bundleRelease all pass.
Still unverified: the Android notification changes from v0.8.0 have no on-device acceptance — no device or emulator is attached to the build machine. Tracked in Roadmap_Blocked.md.
The APK is unsigned — no release signing key is generated or committed for this project. Install with adb install -r, or build and sign your own from android/.
Drains the 2026-08-18 audit pass: 21 of 24 findings shipped.
User-configured egress was silently dead. The strict connect-src allowlist added in v0.6.0 is correct for the app's own feeds, but three features fetch hosts only the deployer can know — the webhook alert sink, the remote GeoJSON overlay loader, and receiver coverage. All three were refused by the policy and reported it as a generic "Failed to fetch", indistinguishable from the host being down, while the settings copy and README still advertised them as working. They now watch for the securitypolicyviolation event and name the exact host to add to connect-src in index.html and _headers. Receiver coverage additionally reports the mixed-content case, which no CSP change fixes: an HTTPS page cannot reach an http:// LAN feeder.
Privacy-protected aircraft were named in shareable URLs. buildViewUrl was guarded and tested, but buildUrl — which writes the address bar through replaceState, the URL a user copies by hand — and generateLink, behind the Share Flight button, both emitted the PIA hex, and generateLink emitted its live position alongside it. All three builders now apply the same rule.
Keyboard shortcuts M/V/A drove the hidden mobile filter chips instead of the desktop filter. Offline mode re-toasted and rebuilt every marker every six seconds. The service worker's API cache grew without bound. Every alert sound leaked an AudioContext until the browser's cap was hit and sounds stopped. Background probes duplicated what the live loop already measured, on a shared rate-limited relay. User-supplied names went into markup unescaped. The coverage view toasted success while painting an invisible canvas under ?renderer=webgl, and its sampling had no off switch. The OpenSky credential slot watched storage keys nothing ever wrote. The viewport CSV export was vulnerable to spreadsheet formula injection. Toasts cut each other short. Importing a backup reset settings it did not carry.
Android: an alert arriving before notification permission is granted is now held and posted once granted rather than discarded, and tapping a notification selects the aircraft that fired it — the viptrack_hex extra had been written and never read.
About 300 lines of Phase-16 reliability scaffolding — retrySystem, CircuitBreaker/circuitBreakers, errorRecovery — that had no callers, ran two live timers, and implied protections that did not exist.
59 static contract tests, 35 Playwright runtime tests, security-header and CDN dependency gates, plus testDebugUnitTest lintDebug assembleRelease bundleRelease all pass. A new gate fails the suite if CRLF reaches a hand-maintained source.
Not verified: the Android notification changes have no on-device acceptance — no device or emulator is attached to the build machine.
The APK is unsigned — no release signing key is generated or committed for this project. Install with adb install -r, or build and sign your own from android/.
Self-hosted PMTiles basemap (opt-in). The MapLibre lane (?renderer=webgl) can now read a .pmtiles archive served from your own origin over HTTP range requests, removing the last third-party basemap dependency. Build one with py -3.13 tools/build_basemap_pmtiles.py. Measured against the Protomaps daily planet build (127.9 GB): world zoom 0-6 is 42.7 MB, zoom 0-7 is 178.4 MB, and a CONUS zoom 0-10 build is 361.1 MB, so only the first is viable against the GitHub Pages budget and the build script refuses more without --allow-large. Cold load is 10 range requests and about 480 KB; vector tiles overzoom, so a zoom 0-6 archive still draws past its maximum zoom. The archive is intentionally not committed - it has to be rebuilt as the data ages and each rebuild would add its full size to git history - so a checkout without one falls back to the normal basemap. Archive paths are same-origin only, because connect-src is a real allowlist.
Coverage view. Accumulated local observations now render as a density heatmap or persistent tracks over a selectable window (last hour, 6 hours, 24 hours, 7 days) at a configurable 15 s to 5 min sample interval. The trailHistory store had a writer and no call sites, so the previous heatmap only ever showed the current in-memory session. Points aggregate into cells during the read, so a redraw is bounded by what is on screen rather than by how long the store has been running - under 250 ms at 60,000 stored points - and the walk stops at 250,000 points and says so instead of locking the tab. Privacy-protected aircraft are excluded when sampled and again when drawn. The style and window travel in shared view links; no identities do.
Also in this release: a single settings surface for API credentials with a leak test, tar1090-style regex filters reaching type code and description, shareable analyst view links, restored Android 16 back navigation, and WCAG 2.2 SC 2.5.7 / 2.5.8 conformance.
56 static contract tests, 21 Playwright runtime tests, security-header and CDN dependency gates, and testDebugUnitTest lintDebug assembleRelease bundleRelease all pass on Windows 11 with JDK 21 and Android SDK 36.
The APK is unsigned - no release signing key is generated or committed for this project. Install with adb install -r, or build and sign your own from android/.
Full changes: see CHANGELOG.md in the repository.
Access-Control-Allow-Origin, and the source manager was short-circuiting relayed sources to "degraded" on GitHub Pages, so the hosted build could not reach a single feed. All four feeds are now marked relay-only and checked through the CORS relay.api.codetabs.com, which no longer answers and only consumed the request timeout./lat/{lat}/lon/{lon}/dist/{d}, not /point/..., so every health check against it had been failing with HTTP 400. ADSB.fi has no /pia endpoint, which is now modelled rather than fetched twice.base_reflectivity_mosaic, which also covers Alaska, Hawaii, the Caribbean and Guam. A tile failure now falls back to RainViewer's global mosaic instead of leaving the overlay blank, and the toggle and its button state track whichever layer is live.maximum-scale=1.0, user-scalable=no, a WCAG 2.1 SC 1.4.4 failure that mattered more once the mobile flight deck became a first-class surface.prefers-reduced-motion is now honoured in assets/viptrack-ui.css, which owns the mobile deck and had no handling at all, and aircraft marker interpolation snaps to position instead of animating.forced-colors: active support so borders, focus rings and status dots survive Windows High Contrast, where author colours are discarded and several controls are distinguished by colour alone; prefers-contrast: more raises border and dim-text contrast.tools/refresh_reference_data.py refreshes the vendored aircraft database from tar1090-db and records its provenance in data/aircraft/manifest.json (upstream version, licence, row count, refresh date). --check reports the age without downloading, and a contract test fails once the recorded build is more than 120 days old � the checked-in copy had drifted five months behind with nothing to notice.
tools/test_runtime.py: behavioural acceptance that boots the real page in Chromium with the network stubbed from captured fixtures. Eight tests cover feed rendering, filter switching, the aircraft detail panel, the degraded-source indicator, keyboard operation of the status panel, a settings toggle actually changing and persisting the setting it names, radar on/off, and a file:// boot. Service workers are blocked at the context level so nothing reaches the real network. Mutation-verified: with two regressions injected the runtime suite fails while the 51-test static suite stays green.
Android watchlist alerts now raise real notifications. WebView implements no Web Notifications API, so new Notification(...) was silently inert in the app; alerts route through a VIPTrackAndroid.notifyAlert bridge that creates a high-importance channel, requests POST_NOTIFICATIONS on first use rather than at launch, and deep-links back to the aircraft that fired. One notification per aircraft, so repeats replace instead of stacking.
A live feed status control. The reliability indicator existed but was switched off with a global display: none, so an outage looked exactly like normal operation. It is now visible, colour-coded healthy/degraded/unhealthy, counts only enabled sources, and opens a panel listing every source with its status, last success age, recent error count, whether it is relayed, and � for a disabled source � why. The panel also shows how old the plotted aircraft data is. Closes on Escape or an outside click and stays clear of the ethics notice and the mobile aircraft peek card.
:root, assets/viptrack-ui.css, then applyMidnightTheme() setting six tokens inline on documentElement � and the shipped colours are --bg #0a0a14 / --accent #00d4ff, not the values previously documented. Each layer now says where it sits in that order. Also corrected the README's localisation key count (342, not 313).Deleted data/interesting/ and data/aircraft/aircraft.csv. Every file in data/interesting/ was byte-identical to a copy already served from its canonical path, and aircraft.csv was a byte-identical duplicate of registrations.csv, which is the one the app reads. About 47 MB of the published site was the same bytes twice.
Dropped the sources a browser cannot reach. Planespotters' public photo API now requires a descriptive User-Agent � a header fetch() forbids the page from setting � and it refuses relayed requests, so it is unreachable from a browser-only app by construction; its two priorities left the photo chain and the working airport-data.com/hexdb.io/local-silhouette fallbacks remain. globe.airplanes.live answers 403 through every relay, so remote trace fetching is disabled (traceUrl: null, still the switch to re-enable it) and trails come from the locally recorded history with an honest status message instead of two dead round-trips per selection. Its aircraft_sil and airline_banners paths answer 404 and were replaced with the SkyTrack mirrors. The link-outs to planespotters.net still work. Both hosts left the CSP.
Untracked and deleted four artifacts that were published with the site but are not part of it: index.html.bak2 (533 KB), a 1.1 MB .mhtml page capture, a 1.3 MB root icon.png, and the photo-audit.html dev page. .gitignore covered *.bak but not *.bak2; it now covers *.bak[0-9] and *.mhtml.
connect-src is an allowlist again. Both the meta policy and _headers carried bare http: and https: sources, which match every origin and made the 28-entry list that followed them decorative. Removed them, added the vector-basemap and OurAirports hosts the app actually fetches, and added object-src 'none' to the meta policy. img-src deliberately stays scheme-wide, documented in place.Refreshed the aircraft database from tar1090-db 3.14.1687 (2026-03-07) to 3.14.1713 (614,965 rows).
A throttled relay no longer reads as dead feeds. Every aggregator is reached through the CORS relay, so one relay-side HTTP 429 used to mark all four sources unhealthy and the app reported "No sources" while the feeds were fine. Relay health is now tracked separately: a relayed source that fails while the relay is unhealthy is held at degraded and flagged blockedByRelay rather than counted out, the relay gets its own row in the status panel naming the active host and its error, a 429 backs off for two minutes instead of retrying every six seconds, and the indicator tooltip says "No source reachable: �" when the relay is the cause.
The FAA registry snapshot now ages out of owner identity. FAA �803 (FAA Reauthorization Act of 2024) lets private owners request withholding at any time, so a frozen shard set drifts from "privacy-minimised" toward holding records an owner has since asked to be withheld. Owner details are labelled with the snapshot age after 90 days and withheld entirely after 180, while type, model and year � which no withholding request covers � survive indefinitely. The aircraft panel shows the snapshot date wherever owner identity appears, and the README documents the regeneration command.
Reference data now loads from this repository instead of a sibling one. Every dataset was configured with primary: pointing at raw.githubusercontent.com/SysAdminDoc/SkyTrack/main/�, with no local path anywhere in the chain � so a tagged release's behaviour could change without a VIPTrack commit, file:// and offline never really worked, and every user's browser hit a personal repo's raw endpoint. All 21 dataset primaries, the six image base URLs and the silhouette sprite now resolve same-origin, with the upstream plane-alert-db mirrors kept as fallbacks and the SkyTrack mirrors retained only for hosts that trim the bulk media trees (the Android bundle ships neither photos nor silhouettes). sw.js caches the same-origin copies too. Outbound requests to raw.githubusercontent.com on a cold load drop from 28 to 6.
Airplanes.live is disabled by default and carries a machine-readable reason: its public endpoint returns HTTP 403 pending approved API access.
All notable changes to VIPTrack will be documented in this file.
Format: Keep a Changelog.
Android artifacts are unsigned by repository policy; Play Store publication remains operator-gated. Releases v0.1.0 through v0.5.0 were never tagged � see CHANGELOG.md for their history.
Release v0.0.1