Clear boundaries. Open engineering.
How the application limits risk, and how to report an issue responsibly.
Report privately
Use GitHub's private vulnerability reporting for OpenDownload. Include the affected version, deployment mode, impact and a minimal reproduction. Do not put exploit links, session cookies, credentials or sensitive logs in public issues. There is no response-time guarantee for this volunteer project.
Guarded public-only networking
The supported topology routes extractor requests through a guarded egress proxy. It validates destinations and pins public IPs, rejecting private targets and unsafe DNS answers. The cloud profile checks its required namespaces at startup and refuses to open a public listener if isolation is unavailable.
Ownership and resource limits
Files belong to the browser session that created the job. Same-origin mutations, bounded queues, scratch/output limits and temporary retention limit common abuse paths. The public cloud profile uses one worker, three queued/active jobs, a 128 MiB job limit and 15-minute retention. These limits do not establish arbitrary public-traffic capacity.
Support and limitations
The latest 0.1.x patch is the supported release line. Experimental branches are not supported releases. The cloud profile shares a container and filesystem between components; it is not a separate VM per download. No independent audit or security certification is claimed. Read the full threat model before operating a public instance.