Awesome Raspberry Pi - Curated Resources for Raspberry Pi Projects

thibmaek/awesome-raspberry-pi is a curated list of Raspberry Pi resources — operating systems, projects, hardware guides, software and tooling — released into the public domain under CC0.

A list of links is only as good as whether the links still work, so we measured that rather than describing the categories.

The audit

We cloned the repository and extracted every GitHub repository link from the README: 325 total links, of which 111 point to distinct GitHub repositories. Then we asked each one whether it still exists, using the cheapest check available:

git ls-remote --exit-code https://github.com/<owner>/<repo>.git HEAD

Result: 109 of 111 reachable. Two gone — Scottcjn/Rustchain and besoeasy/telepi.

That is a rot rate of 1.8% on a list whose entries accumulated over years, and it is a genuinely good number. For comparison, we ran the same audit on two other curated lists and got 0% on one and 2.7% on another, with the difference traceable to a single file.

Two honest caveats about the method. git ls-remote follows GitHub’s redirects, so a repository that was renamed still reports as present — this detects deletion and privatisation, not renaming. And a reachable repository is not necessarily a maintained one; existence is a lower bar than usefulness.

Why this list stays clean

The answer is in .github/workflows/ci.yaml, which is seven lines of configuration doing the work of a maintainer:

on: push
jobs:
  lint_md:
    steps:
      - uses: actions/checkout@main
      - uses: gaurav-nelson/github-action-markdown-link-check@v1
        with:
          file-path: './README.md'

Every push runs an automated link check across the entire README. A dead link fails CI, which means it gets noticed and fixed rather than quietly accumulating.

This is the mechanism behind the measurement, and it is the single most useful thing to know when evaluating any curated list. A list with automated link checking stays usable indefinitely. A list without it decays at a rate set by how often its maintainer manually re-reads several hundred URLs, which in practice is never.

So when you find an awesome list, look in .github/workflows before you look at the content. It tells you whether you are reading a maintained resource or an archaeological record.

The commit history agrees: the most recent change at the time of writing was from 2 October 2026, adding a new entry. This is a list that is still being curated.

What is actually in it

The GitHub links are under a third of the total. The rest is where the list’s distinct character shows:

24 links to magpi.raspberrypi.com — the MagPi magazine, which is the official publication and an unusually good source of project write-ups.
26 links across raspberrypi.org and raspberrypi.com — first-party documentation and foundation resources.
12 links to play.google.com — Android apps for managing a Pi from a phone.

That distribution matters for how you use it. This is not purely a software index; it is a mixed list of official documentation, magazine projects, community software and companion apps. If you are looking for “what can I do with this board,” the MagPi and foundation links are more valuable than the repository list. If you are looking for software to run on it, the GitHub section is.

How to get value from it

Curated lists reward a specific reading strategy, and it is not reading top to bottom.

Search it, do not browse it. Open the raw README and search for the thing you have — your sensor, your use case, your language. A 379-line list is faster to grep than to skim.

Use it as a starting point, not an answer. The list tells you a project exists. It does not tell you whether it has been updated since 2019. Check the last commit on anything before you install it — the same thirty-second check that revealed the problem in our review of miflora-mqtt-daemon, an otherwise sensible Pi-adjacent bridge whose last compatibility fix was written for a 2023 platform release.

Prefer the firmware-level answers for anything you depend on. For sensors and automation specifically, a Pi running a bridge daemon is a more fragile arrangement than a microcontroller running ESPHome, because there is no third-party integration in the path to go stale. The Pi is better used as the thing that collects and serves, which is where the self-hosting archive picks up.

Contribute back when you find a gap. CC0 and an active maintainer means a pull request adding something you use is likely to land, and it is the cheapest way to improve a resource you rely on.

The finding: this list has a 1.8% dead-link rate across 111 GitHub repositories, and the reason is seven lines of CI running an automated markdown link checker on every push. Check for that workflow file in any curated list before trusting it — it predicts the list’s usefulness better than its star count does.