# Strata tags nightlies ahead of its own manifest version

> A keyboard-first file manager for Linux with three view modes and a heavy dependency list. Its installer does more verification than the pattern it uses usually allows, and its release tagging tells you which artefact you actually have.

**lgse/strata** — A fast, keyboard-first file manager for Linux

- Repository: https://github.com/lgse/strata
- Website: https://stratafiles.io/
- Stars: 557 · Forks: 56
- Language: Rust
- License: MIT
- Published: 2026-09-17 · Updated: 2026-09-17 · Language: en
- Canonical page: https://hysenlabs.com/projects/lgse-strata

## Nightly tags sit ahead of the version in the manifest

The three most recent releases are all nightly builds with a date appended, and the newest one is dated the same day as the last push to the repository. The manifest in the repository declares a version one minor series behind, which is the normal arrangement for a project that tags continuously from its development branch and only moves the manifest when cutting a real release. It has one practical consequence for anyone auditing what they installed. A nightly is not the version in the manifest, so the number you see in a nightly build tells you nothing about what the manifest would say, and the manifest tells you nothing about which nightly you have. Both are true at once. If you need to reproduce what you are running, record the tag you installed rather than reading the version out of the binary or comparing it to the manifest.

## The installer verifies a digest and a build signature

The installation route is the familiar pattern of piping a remote script into a shell, which is the pattern that most deserves suspicion. This one is paired with verification steps that are not universal:

```bash
curl -fsSL https://raw.githubusercontent.com/lgse/strata/main/install.sh | bash
```

Before installing anything from the release archive, the installer checks both the published digest and the build provenance published alongside it. The second of those is the stronger signal, because a digest proves the bytes match what someone published while provenance proves who built them and from what workflow. The script also shows every privileged package operation before asking to run it, which means the one thing a blind installer hides from you is the list of commands about to touch your system. The binary itself goes to a per-user location rather than a system one, so the install does not need to own the machine to give you the program.

## Unattended mode installs the minimum and nothing else

For a scriptable install there is a non-interactive flag, and the documentation is unusually careful about what it does not do. Non-interactive installs the required dependencies and the binary without prompting, and optional integrations stay disabled unless you select them explicitly. Several flags imply non-interactive, so passing any of them removes the prompts. The implications stack: folder association implies the desktop entry and the file-manager integration, and the file-manager flag on its own enables only the open-file-location behaviour. File chooser replacement is deliberately excluded from all of it, requiring a separate opt-in flag, or a separate flag to refuse it and dismiss the one-time in-app offer. So neither an unattended install nor a folder association will silently replace your chooser. That is two explicit exclusions protecting the two settings people complain about after the fact.

## The installer refuses to install the unlock helper itself

Encrypted-volume unlock is the one integration with a stated boundary. On the primary desktop environment it is offered for versions three and four, the installer asks, and the default answer is no. On a generic Arch installation it is offered only when the helper package is already on the path, and the installer never installs that package itself. An unattended install needs the explicit flag, because non-interactive alone and every other opt-in flag leave it declined. Restoration differs by platform: on Arch you restore by running the binary with the uninstall flag, while in the settings only the primary desktop environment offers that restore, and the documentation says so directly. Non-interactive package installation also needs passwordless privilege escalation or cached credentials, which is the other thing that will stop a provisioning script on a locked-down machine.

## Archive support is a default feature, not an opt-in

The manifest declares a small set of features and the archive support is in the default set, gated on a pair of native dependencies. Most projects make the reverse choice, since a native library is exactly the kind of thing that fails to build on an unusual machine. Here the default build pulls in the archive libraries unless you build with no default features, which means a source build for an unusual architecture needs an extra flag rather than an extra memory. Everything else in the dependency list points the same way. There are two graphics backends as separate entries, so both a Wayland and an X11 path are compiled in, which is consistent with the claim that it works on compatible environments while being designed for one specific desktop. There is a Linux sandboxing library and a call filter compiler, a JavaScript engine, a vector renderer, an HTML parser and a spreadsheet reader, all in the same set.

## Global search covers local drives and stops there

The recursive search is the feature with the clearest stated boundary. A key combination finds files and directories by name or by path, and it works while the directory tree is still being indexed, so you are not waiting on a full walk before you can start typing. Global search covers the home directory and all mounted local drives regardless of the current folder, and hovering the search field shows which locations are included. The dialog warns when results are incomplete, which is the right behaviour for a search that may still be catching up. Folder-scoped filtering stays separate from this. And the boundary: URI-native remote shares are not yet included. Remote locations are browsable through the location field, including authenticated network shares and remote servers with explicit host-key decisions, but they are not searched globally.

## Previews run through real parsers, and the parsers are listed

The preview system is described in two categories and the distinction is worth keeping. Native rendered Markdown and static HTML are the first category, meaning the content is actually laid out rather than shown as source. Everything else is a bounded preview: text, source code, images, camera raw files, documents, audio and video. The phrase that matters is that native parser-backed formats are isolated from the application, which reads as an admission that these libraries are the fragile part and are kept behind a boundary. The properties view is where the metadata work shows. It reports media resolution, duration, bitrate, codecs and audio and video rates, and for raw photos and properties it also reports dimensions, camera, lens, focal length, shutter speed, ISO and GPS coordinates, with an explicit placeholder for values that are not available rather than a blank.

## Conclusion

Use Strata if you want spatial column navigation on a modern Linux desktop and value that the installer shows you privileged operations before running them. Before you install unattended, read the flag implications, because the non-interactive mode installs only what is required and leaves every optional integration off unless you name it, and the encrypted-volume unlock needs a helper package you must install yourself. Check your glibc version first, since current binaries require 2.39 or newer, and confirm whether you want a nightly, because a nightly is ahead of the version the manifest declares.

## FAQ

### how to install strata

Pipe the install script into a shell, or run it with a non-interactive flag for an unattended setup. Arch Linux and the primary desktop environment are the supported targets, current binaries require glibc 2.39 or newer, and the binary installs per-user at a location in your home directory.

### how to use strata

It opens in a spatial column browser and also has an icons grid and a sortable list table. Navigation, history, location entry, filtering, fuzzy search, file operations and quick previews are all reachable from the keyboard, with an optional footer and a function-key shortcut reference.

### What are the Strata system requirements?

Current binaries require glibc 2.39 or newer plus a list of runtime libraries, and it works on compatible GTK4 Linux environments. Arch Linux and the primary desktop environment are named as the primary supported ones.

### Does Strata work on Wayland and X11?

The dependency list declares both a Wayland and an X11 graphics backend as separate entries, so both paths are compiled in. The manifest keywords include both wayland and gtk4.

### How does the Strata installer verify what it downloads?

It verifies both the published digest and the build provenance from the release workflow before installing anything, and it shows every privileged package operation before asking to run it.

### Does Strata search remote shares?

Not yet. Global search covers the home directory and mounted local drives, and the dialog warns when results are incomplete, but URI-native remote shares are excluded. Remote locations can still be browsed through the location field.

## Sources

- [lgse/strata on GitHub](https://github.com/lgse/strata)
- [License: MIT](https://github.com/lgse/strata/blob/main/LICENSE)
- [Project website](https://stratafiles.io/)
- [README](https://github.com/lgse/strata/blob/main/README.md)
- [Releases](https://github.com/lgse/strata/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/lgse-strata