Skip to content

Security and Support

Lucas (SatoshiUNO) edited this page Oct 5, 2026 · 29 revisions

Security and support

ALPHA — USE AT YOUR OWN RISK. .SYSTEMX is experimental and may change daily. Pin a reviewed release, keep recoverable backups, and validate it in your project. Template checks do not certify production readiness. See release policy.

Current alpha: 1.8.7-alpha.1 · Alpha1 branch

.SYSTEMX is alpha: use at your own risk, expect possible daily changes, and pin a reviewed release. Start with first-time setup, release policy, and uninstall and cleanup.

For bugs, questions, and feature requests, use GitHub Issues. Include systemx --version, the selected defaults version from systemx status --target PATH, OS/Python version, setup profile, expected behavior, and a minimal reproduction in a temporary project. An old copied root VERSION may differ from the active defaults; report both when relevant.

Review and redact logs before posting. Status and operation receipts can contain local paths; exported context can contain private project data. Share only the smallest sanitized evidence needed. Sensitive vulnerabilities use the private reporting path.

Support is community/maintainer best effort, without an SLA or guaranteed release date. This project does not operate a hosted service, manage your cloud accounts, or install an MCP server. A passing template check is not a production audit.

Private security reports

.SYSTEMX is experimental alpha software, provided under the MIT License without warranty. It is not a production-readiness or security certification.

Report suspected vulnerabilities privately through GitHub private vulnerability reporting. That repository feature is enabled. Include the affected release/tool version, platform, expected boundary, and minimal sanitized reproduction. Never include credentials, customer information, or private project records in a public issue.

Reports are reviewed as maintainer capacity permits. There is no guaranteed response time, supported-version window, or backport commitment during alpha. Report issues in older releases too and identify the affected versions; do not assume an older numeric version is security-supported. Corrections will identify their affected and fixed versions when known.

The template manager downloads explicitly selected defaults and can run configured project commands with the caller's permissions. Review publishers, sources, commands, and target paths. Distribution fingerprints check consistency with their manifest; they do not independently authenticate a publisher. The selected release cache is checked for unexpected files, links, and directories before its Python runner executes. For an exact remote tag, an independently obtained --archive-sha256 digest can pin the downloaded codeload ZIP before parsing; opted-in startup discovery has no such independent pin. See installation and updates. Direct manager, runner, and release-script entry points enter Python -I mode before imports. Named local helpers load from their source bytes, blocking unlisted local modules and substituted .pyc files in those direct paths. The installed systemx console entry point resolves its package using the initial Python import paths before restarting in isolated mode. If PYTHONPATH or the working directory is untrusted, start a reviewed virtual environment's Python with -I -B -m systemx so the first import is isolated. Library imports inherit the host application's Python trust environment. These guards do not authenticate those named source files, a publisher, or the host Python installation. Use a trusted interpreter and package installation. The optional white-paper tools also start isolated, accept only HTTPS and internal PDF links, and reject linked figure roots. On POSIX systems, they anchor output writes to an opened directory and reject linked final outputs; the legacy PDF builder also rejects hardlinked outputs. Native Windows publication fails closed until equivalent directory-descriptor protection is available. A published paper edition is preserved in place; build a separate draft before publishing a new edition. See the research paper format. Fresh setup refuses conflicting executable defaults; updating an older managed installation may require an explicit, backed-up bootstrap refresh. That refresh handles eight recognized stock bootstrap and launcher files; it can add a genuinely absent historical stock file, while backing up only files it replaces. The current manager newly selects releases 1.8.7-alpha.1 or newer. An already selected verified older snapshot can run through a compatibility shim while a reviewed migration is prepared; its old code retains historical limits. GitHub's immutable-release setting protects releases published after it was enabled on 2026-10-05; earlier releases are not retroactively protected. Avoid administrator privileges, protect project data and operation logs, coordinate writers, and keep recoverable backups.

Project-specific security guidance remains in .SYSTEMX/docs/SECURITY.md. Adopting projects must define their own security contacts, deployment boundaries, and incident process.

DOT SYSTEMX · User manual

1. Start here

2. Work and continuity

3. Setup and maintenance

4. Advanced reference

5. Project information

Repository · Use this template · MIT license

Clone this wiki locally