Security · GShips

Current public-alpha boundary

No accounts, comments, uploads, advertising trackers, session replay, or generic chatbot are in scope. Forms require strict same origin, bounded streaming bodies, server validation, HMAC rate limiting, prepared statements, minimal retention, and operational review. A daily scheduled cleanup removes expired form data. Do not send exploit details through ordinary forms; use security.txt.

Accountability

Material corrections receive a dated record. Publisher-level commercial interest is disclosed; no independent review council is currently staffed.

Security policy foundation · Owner-alpha foundation · Independent review pending · Suggest a correction

How to inspect this page

Scope: GShips page /security

Citation applicability: This project or directory page introduces navigation and editorial procedure; evidence-bearing conclusions remain in its linked records.

Assumptions and limits

This page is a public-alpha editorial synthesis, not a validated generation-ship design or mission authorization.
The page remains bounded by the cited or linked records and does not inherit evidence from uncited context.

What would change this page?

Material corrections, independent review, changed source evidence, or a changed project boundary would trigger a dated revision.

People, review, and conflicts

Prepared by: GShips Project
Editorial status: public-alpha accountability pass
Editorial reviewer: GShips Project AI-assisted editorial synthesis
Last editorial review: 2026-07-26
Independent review: pending
Independent reviewer: No independent reviewer assigned
Last independent review: No independent-review date exists
Last content edit: 2026-07-25

Declared conflicts

The maintainer intends to explore a commercial venture based on some GShips work. No entity, outside funding, customer, sponsor, or indexed-organization relationship currently exists.

Suggest a correction to this page