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
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