[LOGO] UNRAID OS

Open Beginner friendly

#2,505 opened on Aug 10, 2026 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 68/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Quiet
Tech stack: c
Domain: cli

Research direction

Start with the Unraid OS os-release block and ASCII art in issue #2505, then inspect the existing distro-logo definitions in fastfetch to find where this entry belongs. Done means Unraid OS is represented with the submitted colored artwork and its stable metadata, while the checklist constraints remain satisfied.

Written by the indexing model from the issue text.

Description

logo request

OS

cat /etc/os-release
NAME="Unraid OS"
ID="unraid-os"
ID_LIKE="slackware"
PRETTY_NAME="Unraid OS 7.3 x86_64"
CPE_NAME="cpe:/o:limetech:unraid-os:7.3.2"
VERSION="7.3.2 2026-07-08"
VERSION_ID="7.3.2"
VERSION_CODENAME="stable"
HOME_URL="https://unraid.net/"
SUPPORT_URL="https://support.unraid.net/"
BUG_REPORT_URL="https://forums.unraid.net/"
DOCUMENTATION_URL="https://docs.unraid.net/"
VENDOR_NAME="Lime Technology, Inc."

Public repository URL

https://unraid.net/getting-started

Distro Website

https://unraid.net

ASCII Art

                     $3█  ██ █
                     $3██  █  ██
     $2██           $3██ ██     ██ ██
     $2██           $3██           ██
     $2██ ██     █  ██           $3██
     $2██ ██     ██ ██           $3██
        $2██  █  ██
            $2█

Original Image URL

No response

Checklist

My distro has reached a stable state (out of beta, alpha, RC).
The ASCII art is smaller than 50x20 characters (W x H).
The ASCII art uses $N color placeholders (or colors are natively available in os-release).
The ASCII art has no unnecessary trailing spaces at the end of lines.
I promise that I will send a removal request if the distro is discontinued.

Dominant language: C
Stars: 24.7k
Forks: 895
Avg merge: 1d 4h
Merged PRs (30d): 16

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

wm_gcp_parse_output underflows its heap buffer by one byte Open

level/task module/gcp type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

wazuh/wazuh#39525 · Opened Sep 21, 2026
Build failure with newer clang Open

Difficulty 1/5 Under an hour Newbie friendliness 86/100

hapostgres/pg_auto_failover#1190 · Opened Sep 21, 2026
Use name macOS not darwin in release table Open

docs

Difficulty 1/5 Under an hour Newbie friendliness 85/100

visit-dav/visit#21164 · Opened Sep 21, 2026
[copp] test_copp.py missing BGPv6 test coverage Open

P3 sonic-vpp

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

sonic-net/sonic-buildimage#29662 · Opened Sep 21, 2026
py-msgpack depends on c not cxx in build step Open

Difficulty 1/5 Under an hour Newbie friendliness 94/100

spack/spack-packages#6586 · Opened Sep 21, 2026

More C issues