Jens/geointel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge repository hygiene guidance

Browse Source 
# Conflicts:
#	SECURITY.md
This commit is contained in:
Jens
2026-08-31 20:23:58 +02:00
parent 21a7bfb6ac db73a0c6ae
commit dcd67b11d1
4 changed files with 54 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex-input/.gitignore
+3
View File
@@ -0,0 +1,3 @@
# Local AI/import workspace. Never commit generated inputs, databases, archives or screenshots.
*
!.gitignore
CONTRIBUTING.md
+12
View File
@@ -0,0 +1,12 @@
# Contributing
Keep GeoIntel changes reproducible, privacy-preserving and free from generated workspace state.
- Branch from the protected default branch.
- Use synthetic or explicitly redistributable imagery, coordinates and datasets in tests and documentation.
- Do not commit `.codex-input` contents, SQLite/WAL/SHM files, archives, contact sheets, model outputs, private maps, credentials or local deployment data.
- Document the origin, license and intended use of every external dataset, model and media asset.
- Add tests for behavioural changes and run the documented backend, frontend, geospatial and managed validation gates.
- Explain data-model, coordinate-system, model, privacy and deployment impact in the pull request.
Report security issues according to `SECURITY.md`.
SECURITY.md
+23 -6
View File
@@ -2,19 +2,36 @@
## Supported code
Security fixes target the current `main` release line. Historical research, calibration and development branches are not supported release channels unless explicitly documented otherwise.
Security fixes target the current `main` release line. Historical research,
calibration and development branches are not supported release channels unless
explicitly documented otherwise.
## Reporting vulnerabilities
Report suspected security issues privately to the repository owner. Do not publish credentials, access tokens, private infrastructure details, personal data, sensitive geospatial source material, proprietary datasets, production database contents or exploit-sensitive evidence in a public issue.
Report suspected security issues privately to the repository owner. Do not put
credentials, access tokens, private infrastructure, precise sensitive
locations, proprietary imagery or datasets, model artifacts, production
database contents, personal data or exploit-sensitive evidence in a public
issue.
Include the affected commit/component, minimal reproduction conditions using synthetic or public data where possible, expected and observed behaviour, impact, and whether the issue affects authentication, authorization, uploads, archive handling, file paths, report/export generation, AI/model loading, container/deployment boundaries or secret handling.
Include the affected commit and component, minimal reproduction conditions
using synthetic or public data where possible, expected and observed
behaviour, impact, and whether the issue affects ingestion, geospatial
processing, authentication or authorization, uploads, archive or path handling,
model inference, reports and exports, deployment, data retention or secrets.
## Repository and data hygiene
## Repository and data boundary
Local Codex inputs, calibration databases, contact sheets, runtime data, generated reports and cross-project scratch are not release source and must stay outside version control. The repository ignore rules and release gates are part of this boundary.
Geospatial inputs and derived outputs can reveal people, assets and sensitive
locations. Treat screenshots, contact sheets, coordinates, source archives,
SQLite/WAL state, model output and exports as potentially sensitive. These
belong in controlled external storage, not the source repository.
Never commit live `.env` files, production backups, credentials, operator data or private datasets. Public examples and tests should use synthetic or explicitly redistributable material.
Local Codex inputs, calibration databases, runtime data, generated reports and
cross-project scratch are not release source. Never commit live `.env` files,
private keys, production backups or databases, customer or operator data,
unpublished imagery, credentials or private datasets. Public examples and tests
must use synthetic or explicitly redistributable material.
## Disclosure
docs/REPOSITORY_SANITATION.md
+16
View File
@@ -0,0 +1,16 @@
# Repository sanitation status
The current-tree hygiene campaign removed committed local AI/import artifacts from `.codex-input`, including SQLite databases and WAL/SHM state, archives, generated JSON, geometry diagnostics and large contact-sheet screenshots. A deny-by-default `.codex-input/.gitignore` prevents recurrence.
## HISTORY_REWRITE_REQUIRED
Deleting these files from the current tree does not remove their objects from reachable Git history. A later owner-approved history phase must inventory all refs and remove or explicitly retain the historical objects after evidence and backup review.
| Path family | Information type | Why history sanitation is required |
|---|---|---|
| `.codex-input/*.db`, `*.db-wal`, `*.db-shm` | local application/database state | may contain records and internal processing state; WAL/SHM files are runtime artifacts |
| `.codex-input/*.tar`, `*.tar.gz` | source/workspace snapshots | duplicate source and potentially private repository content |
| `.codex-input/*contact_sheet*.png` | generated screenshots/imagery | may expose source imagery, UI state or sensitive locations |
| `.codex-input/*.json`, geometry diagnostics | generated analysis/evidence | may contain private inputs, coordinates or operational context |
Before any public review, perform a bare-clone all-ref secret, path, database/archive, media and large-object scan. No history was rewritten during this campaign.