An Electron port of js-tetris, with TypeScript, React, and webpack. js-tetris is source lineage only; Electris is maintained independently.
There is no supported current Electris binary release.
Historical 2018 ZIP releases are kept only as archival artifacts. They are unsupported, not security maintained, and modernization work does not retroactively make those assets current or supported.
The repository contains guarded tag-driven draft automation for future portable Linux x64 and Windows x64 packages, plus draft-only macOS qualification. Automation is not a release or support claim: tags, publication, GitHub controls, vulnerability reporting, branding review, and macOS signing/notarization require separate authorization or completion. Windows packages are initially allowed to be unsigned and can trigger SmartScreen or “Unknown Publisher” warnings.
For the exact operator flow, assets, trust consequences, support window, and security status, see:
If you choose to inspect those archives, use the repo's Releases page as an archive reference only.
The renderer trust boundary contains only the packaged renderer.html, JavaScript,
stylesheet, and image assets. Production HTML carries this Content Security Policy:
default-src 'none'; script-src 'self'; style-src 'self'; img-src 'self'; connect-src 'none'; object-src 'none'; frame-src 'none'; media-src 'none'; worker-src 'none'; manifest-src 'none'; base-uri 'none'; form-action 'none'
The main process allows the window to load only its exact packaged renderer URL,
blocks redirects, and denies every popup or new-window request. External links never
navigate the Electris window: the isolated preload bridge accepts only the semantic
author and license destinations, which the main process maps respectively to
https://www.jaredgotte.com/ and https://opensource.org/licenses/ISC for the system
browser. It exposes no arbitrary URL capability.
See CONTRIBUTING.md to get started. The authoritative repository
layout, architecture notes, supported environment, commands, generated-file rules,
and validation expectations are maintained in AGENTS.md. Release
readiness, support, and security guidance are maintained in RELEASING.md,
SUPPORT.md, and SECURITY.md.