Safety guide / Evidence first

Is ArtCraft
safe?

Open source improves inspectability, but it does not automatically guarantee secure binaries, reliable file handling, or production readiness.

Last updated:

Secure evaluation environment for open-source creative applications
Visual brief / 01Source, release provenance, file safety, and recovery are separate questions.

The useful answer is not a universal yes or no. It is a short chain of verifiable checks covering where the software came from, what you run, what files you expose, and how easily you can recover.

1. Start from an official source

Navigate through the official ArtCraft site or the official Storytold GitHub organization. Avoid third-party download mirrors, repackaged installers, and advertisements that imitate download buttons.

2. Verify the release

Match the installer to your operating system and architecture. When a release publishes checksums, compare the downloaded file against the official SHA-256 value before running it.

3. Separate security from maturity

A clean malware scan does not prove that an early application safely preserves complex documents. Parser bugs, export mistakes, crashes, and incomplete format support can still damage work.

4. Use disposable test files

  • Duplicate representative projects before opening them.
  • Keep backups outside the working directory.
  • Save, close, reopen, export, and compare results.
  • Do not grant broader file access than the workflow needs.
Our current posture

Suitable for informed evaluation. Not a blanket recommendation for irreplaceable or deadline-critical production files.