SERVICE HEALTH · DOCUMENTATION SUMMARY

Technical evidence you can check.

This page summarizes the available checksum, signature, tested-configuration, and release-limit evidence. The evidence is static; local changes become live only after deployment and another audit.

Product and service technical

RECORDED · NOT VERIFIED

Public website

https://voidscriptor.com/ is the recorded canonical domain. Live response is established only by the check button; this local audit does not prove the redirect or public availability.

AVAILABLE
RECORDED · NOT VERIFIED

Void Scriptor Studio 1.2.0-rc.2

Local records list a Windows x64 installer measuring 32,746,152 bytes and a signed hash f53402cc84ab3e1e15d7870d4c408cb4f4eef7ebdb0487b79f56e56cddfe5ae6. Public file availability must be checked live; this local audit does not prove it.

AVAILABLE
CONFIGURATION-DEPENDENT

Google/GitHub sign-in

The website provides Google and GitHub sign-in buttons with protected sessions. Availability still depends on production settings; this page never displays secret login data.

DEPENDENT
CURRENT CHECK

Website response

This check tests the website server and main files when the button is pressed. It is not uptime history and does not check third-party services.

Not checked yet.

No check in this session.

CHECK
OPTIONAL · LOCAL

Byte connection on your computer

This local connection uses 127.0.0.1:8766 and accepts only allowed origins. The homepage can still use a remote connection or offline mode; this is not a public service.

LOCAL
NOT RELEASED

QOWNER mobile, Linux, and macOS

There is no public installer for these platforms in this release. Do not interpret the label “coming soon” as a release date.

PENDING

Maintainer verification command: pwsh -File tools/verify-release.ps1 -InstallerPath ./VoidScriptor-1.2.0-rc.2-windows-x64-setup.exe -ManifestPath ./release-manifests/VoidScriptor-1.2.0-rc.2-windows-x64.sha256. The sections below explain the signature result and publisher status; a self-issued certificate does not make the publisher trusted by SmartScreen.

EVIDENCE & LIMITS

Technical evidence you can check now.

File fingerprint (SHA-256)

The SHA-256 value is available as static text in the local manifest. A matching value means the file contents are the same as the published file; it does not prove the file’s origin.

Tested configuration

The available tested configuration is Windows 11 Pro 64-bit, Intel Core i5-4570, 32 GiB RAM, and AMD Radeon RX590 GME. This is not an official minimum requirement; minimum CPU, RAM, GPU, and disk space have not been set. Read the tested configuration.

File signature

The local RC.2 check returned Status: Valid with a signing time. The certificate is self-issued, so signature integrity can be checked, but the publisher identity is not yet trusted by SmartScreen.

Security

The website API does not freely accept requests from every origin. The local Byte connection has an allowlist of origins. Browser isolation settings are not claimed to be fully compatible without verifying OAuth login and the local connection; security reports are listed in security.txt.

TECHNICAL DETAIL

Measured storage and connections.

Application data

Sign-in status and error reports are stored in the Windows application support folder, inside VoidScriptor\state and VoidScriptor\diagnostics\crash. The folder location may vary according to Windows configuration.

Projects

If you do not choose a location yourself, the main project folder is in Documents, inside VoidScriptor\Projects. Your chosen location is the primary reference; if the drive is unavailable, the application tells you that a fallback location is being used.

Sign-in and Byte connection

The website uses GitHub or Google for sign-in. The session cookie does not contain a password. The optional Byte connection runs on your computer at 127.0.0.1:8766 and accepts requests from permitted origins.

OFFICIAL LINKS

Continue from the evidence.

Read the getting started guide, release notes, or report a discrepancy with reproduction steps. Production status does not change just because a local file was fixed.