| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| euosint-dist-v1.3.0.tar.gz | 2026-03-19 | 13.7 MB | |
| euosint-dist-v1.3.0.tar.gz.sha256 | 2026-03-19 | 93 Bytes | |
| README.md | 2026-03-19 | 1.9 kB | |
| v1.3.0 source code.tar.gz | 2026-03-19 | 14.8 MB | |
| v1.3.0 source code.zip | 2026-03-19 | 14.9 MB | |
| Totals: 5 Items | 43.4 MB | 0 | |
EUOSINT v1.3
Highlights
- Added hard signal-gating improvements across collection, triage, and map behavior.
- Improved geo integrity and analyst trust with stronger default visibility rules.
- Expanded and curated military installation overlays with region-aware loading.
- Stabilized discovery and source-ingestion workflows for social/intel channels.
What’s New
Signal and UI behavior
- Default map/feed behavior is now Now-only at load.
- History is shown only when explicitly selected by the analyst.
- Region viewport behavior is aligned across primary regions for consistent zoom/center UX.
- Cluster interaction and map overlay lifecycle behavior were hardened to avoid stale visual states.
Overlay and geospatial improvements
- Military overlay now supports region-aware shard loading (Europe, Africa, North America, Asia, Global).
- Overlay switching now correctly unloads previous regional military layers when region changes.
- Military dataset was enriched, then curated to focus on major installations + operational airfields.
- Added preservation logic for sensitive/strategic camp/detention installations (including Guantanamo seed safeguard).
Discovery and source pipeline
- Discovery updated to better support social-signal candidate paths (X/Telegram) for conflict/piracy/terror/intel contexts.
- Added configurable crawl pacing for X ingestion:
X_FETCH_PAUSE_MS- Added social discovery controls:
DISCOVER_SOCIAL_ENABLEDDISCOVER_SOCIAL_MAX_TARGETS
Testing and stability
- Stabilized API rate-limit race test behavior under
-race. - Full race test suite validated successfully.
Upgrade Notes
- No breaking API contract introduced in this tag.
- Existing schema field names (e.g.
authority_*) remain for compatibility, while UI terminology now uses Sources in key analyst-facing locations.