尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
依最近已完成的 8 小時觀測回合間的 GitHub 星號增量排序
LibreDB Studio 是開源資料庫 IDE，部署在你的資料旁邊，而不是你的筆記型電腦上 — 一個瀏覽器標籤頁涵蓋 PostgreSQL、MySQL、MongoDB、Redis 以及另外十三種引擎，並帶有 SSO an
AI 翻譯
使用 Altimate Code 可在資料工程上取得比 Claude Code 與 Cursor 更佳的結果。建構與管理 SQL、dbt、血緣與資料庫工作流程，開源。
AI 翻譯
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權，自行管理介紹，無需管理員核准。
登入並產生驗證檔案，在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案，即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入，將前往登入頁面。登入後請回到此處，再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify，即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
See how wildfires are spreading across Europe — where they are burning right
now, how fast they are growing, and what they have already destroyed.
⚠ Not an emergency service. This map visualises public satellite data,
which can be hours old and is never an official alert. If you are in danger,
call 112 and follow your local authorities.檢視完整 README ↗See how wildfires are spreading across Europe — where they are burning right now, how fast they are growing, and what they have already destroyed.
⚠ Not an emergency service. This map visualises public satellite data, which can be hours old and is never an official alert. If you are in danger, call 112 and follow your local authorities.
Most fire maps answer one question: where is it burning? They show today's dots and forget yesterday's. But the story people actually need is time — fire seasons are getting longer and more intense, and each individual fire has a history: when it started, which way it ran, how much it took.
FireMapper is built around that. Every view is about change over time, and the whole thing is free, open, and needs no account.
Start with the overview — active fires and recent burn scars across Europe. The bar chart along the bottom is one bar per day: click any day to see where fire was burning that day. A badge tells you whether this week is worse than the last.
Click a fire to open its card. The map flies in and everything becomes about that one fire: how big it is, when it ignited, whether it is still growing, which way it is spreading, the nearest town. Its burn footprint is coloured by when each patch caught — and clicking a bar in its history rewinds the fire, so you can watch it grow.
See the damage. For fires that have already burned, a before/after slider compares satellite imagery of the same place — green forest on one side, black scar on the other.
You need uv (Python) and Node.
make setup # install dependencies
make sample # build a demo dataset — no API key, no account
make dev # open the map at http://localhost:5173
That's it — no server, no database to run. The map reads plain static files.
make sample needs no key: the keyless sources (Meteosat intensity, wind) are
real and live, and the fire history is synthetic so the demo is never empty.
Want the real fire history too? Get a free
NASA FIRMS key, drop it in
.env (copy .env.example), then make refresh-full — 30 days of real VIIRS
detections replace the synthetic ones. make refresh-fast updates only the live
layers and never needs a key.
Issues and pull requests are welcome — see CONTRIBUTING.md to get started, and the Code of Conduct for the ground rules.
Good first contributions: more curated historical fires
(pipeline/notable_scars.json is plain data),
translations, colour-blind-safe palettes, or accessibility fixes.
Built on open data from NASA FIRMS, EUMETSAT, Copernicus, Open-Meteo, GeoNames, and OpenStreetMap. Thank you to everyone who keeps those services public.
MIT © Frederic Robinet