Follow the suite

Each of the 44 assessments was pinned September 22, 2026 (the assessed commit): it describes that one commit, and the repositories keep moving. There are three ways to hear about it: our feed, which says what we checked; the repositories' own feeds, which say what shipped; or GitHub notifications on this project.

1 · Our feedSubscribe to Franken Research

Paste this address into any feed reader:

https://fr.zeststream.ai/feed.xml

It is an Atom feed (open it here) with three kinds of entry:

  • Releases of this assessment, with the first paragraph of the changelog entry and a link to the GitHub release.
  • Dated re-checks. When a repository ships something that could change a verdict cell, someone reads the new code and files a dated re-check beside the pinned packet. The packet itself is never edited.
  • The daily census, at most one entry a day: how many of the 44 repositories have commits after their pin, and how many flagged a release, tag, license, or workflow change that triggers a re-check. The numbers are counted from the census file each entry links.

It keeps the newest 50 entries. It does not list individual commits, and it does not repeat upstream release notes. For those, follow the repositories directly.

2 · The repositories themselvesFollow Jeffrey Emanuel's 44 repos directly

Download franken-suite.opml and import it into your feed reader. Most readers have an "Import OPML" or "Import subscriptions" option. You get three things:

  • A Releases folder with each repository's GitHub releases feed (releases.atom).
  • A Tags folder with each repository's tags feed (tags.atom). Some of these repositories tag versions without publishing a GitHub release, so the releases feed alone misses them. Expect some entries to show up in both folders.
  • Our own feed, from option 1.

These feeds come straight from GitHub, not from us. They carry every release and tag as the maintainer publishes it, before anyone here has read it, so a release in them is not a finding. The repository list is read from the assessment packets each time the file is built.

3 · GitHubWatch the repository

On github.com/JYeswak/franken-research, open the Watch menu, choose Custom, and tick what you want:

  • Releases only: an email or notification for each new release of this assessment, and nothing else.
  • Issues: every new issue. A daily watch reads the GitHub API for all 44 repositories and opens one issue per change that could move a verdict cell, labelled watch. GitHub cannot notify on a single label, so filter those in your inbox or open the list of watch issues.
Want to report something?If you spot a release we missed or a finding that looks wrong, open an issue on the repository. Corrections are recorded in the changelog with a date.

Help fix it

Each opens a GitHub issue form with this page’s address filled in. You need a GitHub account.

Made by Joshua Nowak (ZestStream) with AI coding agents. Not affiliated with or funded by Jeffrey Emanuel; Joshua uses his public tools and is a paying subscriber to jeffreys-skills.md.

Source on GitHub MIT licensed