Skip to content

Sources and method

44 projects and 9 relicensed: where every fact comes from, and how stars per week are measured.

Which projects

Open-source projects under the data and AI stack that the fru.dev sites follow: engines, table formats, streaming, pipelines, databases, search and vector, infrastructure, model serving, ML and LLM frameworks. The list is chosen by hand; suggest one with the link on any listing page.

Licenses and their history

The current license is read from the repository's LICENSE file. GitHub's own detection is shown too, and says NOASSERTION for custom or multi-license files (Elasticsearch, Redis, Terraform, MongoDB and others), so those licenses are read from the file itself. Every relicensing is dated by the commit that changed the LICENSE file, with a link to it, and linked to the company's announcement where one exists. Open source here means at least one of the licenses offered is approved by the Open Source Initiative; anything else is source-available. Not legal advice: the LICENSE file is the text that applies.

Forks, foundations and companies

Forks made after a license change (OpenSearch, Valkey, OpenTofu, OpenBao) are dated from their announcement or repository creation. Foundations come from the foundations' own lists: Apache projects from projects.apache.org, CNCF and LF AI & Data hosted projects and their maturity from their landscape files, and the PyTorch, OpenSearch, DuckDB and OpenSSF foundations from their own pages. The backing company is the one that leads or sells the project; companies carry their companies.fru.dev registry slug.

Stars per week

A weekly run takes a snapshot of each repository's stars, forks and open issues. Stars per week is the difference between two snapshots at least six days apart. Until the second snapshot, it comes from OSS Insight's weekly star history for the three weeks from August 31 to September 21, 2026, labelled as such on each project. OSS Insight counts from GitHub events and trails GitHub's own totals, so only its weekly differences are used, never its totals.

The weekly run

Every Wednesday at 13:15 UTC: one GitHub API call per repository (the unauthenticated limit is 60 an hour), the latest release for a rotating slice, and the foundation lists. A change in GitHub's license detection is logged and sent to the owner for review; the curated license moves only by hand, from a source. No model and no paid search are used.

History

Nothing that changes is overwritten silently. Releases, license detection, renames, archives, foundation listings and stars per week each write a row with the old value, the new one, when and the source; star counts go to weekly snapshots. The Changes page lists them and /api/changes serves them. /api/companies lists every backing company with its registry slug, domain and dated items for companies.fru.dev.

About this data

Projects from GitHub (repositories, releases and LICENSE commits), the foundations' own lists and company announcements, refreshed every Wednesday. License changes are set by hand from a source; the LICENSE file is the text that applies. The list grows as new projects are added. Not legal advice. Logos via logo.dev and GitHub; trademarks belong to their owners. Use Suggest a correction on any page.

License changes by email

Only when a tracked project changes its license, foundation or name, at most once a week.

Double opt-in. Unsubscribe any time.