gipper documentation

Security

Only the latest release receives fixes. This is alpha software controlling paid infrastructure; use provider spending alerts and inspect the provider console when cleanup is uncertain.

Reporting a vulnerability

Use GitHub private vulnerability reporting if enabled. If unavailable, open an issue requesting a private contact without including exploit details, keys, account identifiers, or private data. Private reporting must be enabled by the maintainer before the public launch. There is no promised response time.

Trust boundaries

Serverless queues

Serverless TOMLs select an image and optional executable entrypoint. Treat both as code. Handler inputs and outputs pass through the provider queue. Gipper records canonical JSON input hashes and job identifiers, while applications own the actual evidence. The existing Pod custody report and billing reconciliation do not include serverless receipts. Minimum workers are zero, but idle worker tails can bill. The separate serverless reaper only manages recorded, expired temporary endpoints; deliberately deployed endpoints require explicit deletion.