Maintenance, trust and software security

This page explains how Linxira is maintained, where software comes from, what AUR really costs you, and why a distro without a foundation behind it can still be worth trusting.

Maintenance: directly on Arch

Check your machine for known issues with arch-audit; upstream advisories live at security.archlinux.org.

Software sources at a glance

SourceSignedMaintained byRisk
[linxira] first-party repoYesThis project's CILow, build is inspectable
Arch official core / extra / multilibYesArch packagersLow, officially maintained
AURNo (built locally)Any registered userHigh — review it yourself

AUR: disabled by default, read before you build

Only [linxira] and the official Arch repositories are enabled out of the box; no AUR helper is preinstalled. AUR is not a repository — it is a pile of user-submitted build scripts (PKGBUILDs). The package is compiled on your machine, so nobody vouches for its contents.

If you do use an AUR package:

Trust model: no foundation, but verifiable

Linxira is maintained by an individual / small team, without a foundation or company behind it. Skepticism is reasonable, so here is what you can verify yourself:

What we can doWhat we cannot
Publish all sources, build scripts and CI configProvide a 24/7 security response team
Build every package in CI and sign it with the release key shipped in linxira-keyringOffer a legal entity or commercial SLA
Record repository ownership and lifecycle in governance/repositories.yamlMatch upstream's audit headcount
Keep releases traceable (tags, Releases, signed packages)Take responsibility for third-party AUR packages

No lock-in: this is standard Arch — pacman, systemd, the usual /etc layout, the official repositories. You can disable the [linxira] repository and keep only Arch's mirrors at any time; the system still works. That exit path is intentional.

No telemetry: nothing is collected. Only when you explicitly run linxira-config logs collect/upload does a diagnostic bundle leave the machine, through the channel you chose.

How this differs from other Arch derivatives

DimensionLinxiraPerformance-tuned derivativesDelayed-rolling derivatives
KernelArch stockOwn patchset, self-builtMostly stock
Package lagSame as ArchSame as ArchFrozen 2 weeks to months
First-party layerIntegration and management tools (catalog, config-hub, update)Schedulers, kernel flags, tuningInstaller, themes, separate repos

The trade-off: no kernel-level tuning, in exchange for zero lag against Arch security fixes and the ability to debug problems against upstream documentation and forums.

Filesystem compatibility

FilesystemLinux supportNotes
NTFSRead/write; ntfs3 (5.15+) coexists with the new NTFS driver merged in Linux 7.1Best choice for a shared data disk; make sure Windows is fully shut down (Fast Startup off) before mounting
exFATIn-kernel driver, read/writeUSB sticks and external drives, no permission headaches across systems
FAT32In-kernel driver, read/write4 GB per-file limit; fine for the EFI partition and small drives
ReFSNot supportedWindows-proprietary (Dev Drive, Storage Spaces); there is no usable Linux driver, so it cannot be mounted
BitLockerLimitedcryptsetup can unlock with a recovery key depending on the encryption mode; do not share an encrypted partition between both systems long term

The safe pattern for shared storage: create a dedicated NTFS partition for both systems and never mount Windows' own system volume (C:) from Linux — especially not while Windows is hibernated.

Related