We've launched!  Read our announcement.

Our programs

Making the Open Source ecosystems we rely on more sustainable means doing research on topics from software supply chain security to maintainer burnout. We need your support to do our work.

Annual report on OSS maintainer well-being

Understanding the factors affecting the mental well-being of Open Source maintainers and how they change.
Fund
Funded 5,878 GBP
Goal 30,000 GBP

Miranda Heath’s Nov 2025 report on burnout in Open Source amplified maintainers’ stories about their struggles with burnout. She identified causes of burnout including maintainers struggling to make a living and feeling pressured to work a stressful “second shift” after their day job; and being worn down by entitled behaviour from community members.

Miranda is now working on an annual survey of Open Source maintainers, to understand the ongoing factors affecting their well-being. This work is important and timely. Since the last Tidelift State of the Open Source Maintainer survey in 2024, it appears nobody has been regularly collecting data on working conditions in Open Source. This data is needed now more than ever, as the rise of AI coding is creating new pressures on Open Source maintainers in urgent need of effective and data-driven solutions.

By contributing to this fund, you will help ensure that it is always possible to know how the Open Source maintainers we rely on are doing, how this is evolving over time, and where they could most use our support.

Study on the impact of AI on Open Source maintainers

Understanding how AI is affecting the well-being of Open Source maintainers and their projects.
Fund
Funded 0 GBP
Goal 30,000 GBP

In Dec 2026, Miranda Heath released a report on how AI coding affects the mental health and well-being of developers. She highlighted how developers are spending less time writing code, and more time reviewing AI generated code. Less time collaborating with colleagues, and more time wrangling agents. There is pressure to work at greater speeds, and to respond to greater volumes of PRs. These changes are exacerbating existing risk factors for burnout, and leaving many feeling like their identity and craft as a programmer are under threat.

Miranda would like to extend this work by investigating the impact of AI specifically on people working in Open Source. She will conduct in-depth interviews with a diverse sample of people working in Open Source, to get rich, qualitative insights into the impact AI is having on maintainers.

With this data, she will make recommendations about how to address the impacts of AI on Open Source, and protect the well-being of the people who keep it running. By giving to this fund, you will help us to provide evidence-based and truly independent guidance as to how to sustain Open Source, and the people that make it, through the rise of AI coding.

Securing Python's binary dependencies

Improving security by bringing hidden binary dependency relationships to light.
Fund
Funded 0 USD (0 GBP)
Goal (52,531 GBP) 69,120 USD

A large amount of infrastructure relies on Python for its ability to easily interface with compiled libraries, particularly AI and scientific software. However, package management tooling in the Python ecosystem does not record these binary dependency relationships, which most frequently occur when Python code calls compiled libraries written in languages such as C or Rust.

This means that developers cannot track or remediate CVEs in these dependencies; cannot know when these libraries become unmaintained “Bernies”; and cannot offer support to the maintainers of their binary dependencies. Given that around 20.4% of popular Python packages include binary dependencies, this status quo puts critical Python-based technology, from AI to built infrastructure, at risk of cyberattacks and degradation.

We propose a solution then can make a large positive impact on the security of the Python ecosystem with a comparatively small investment; can be integrated as a default into existing tools; and is structured so that it can be, in principle, ported to other language ecosystems in the future.

Resources: Funding proposal

ecosyste.ms Growth Fund

Providing world-class Open Source intelligence tooling to governments, researchers and companies worldwide.
Fund
Funded 27,000 USD (20,520 GBP)
Goal (182,400 GBP) 240,000 USD

ecosyste.ms is the world’s largest public-access source of data on Open Source software. It holds data on 16.6 million packages, 357 million repositories, and 25.8 billion dependency edges, enabling it to know which packages are most critical to society, who maintains them, and how well they’re able to handle the pressures placed upon them. Its users have included Microsoft, the Linux Foundation, the Chan Zuckerberg Initiative, and the Sovereign Tech Agency.

Despite this, ecosyste.ms is currently supported by very little funding from a single-digit number of commercial clients.

Additional funding would help ensure the future sustainability of the service. And it would allow us to develop features to enable policymakers and security researchers worldwide to do their work.

Goals

Providing data on CVE reachability

Package registry data doesn't provide the full picture on CVE reachability. We are able to analyse vendored binaries, patches, and repackaged dependencies to provide richer data on CVE reachability than is currently available.

Helping funders reach maintainers

ecosyste.ms Funds already allows companies to fund OSS they depend on. We aim to expand this service to donors to give to custom funds, increasing the number of maintainers receiving financial support.

Making adoption easier

Adopting ecosyste.ms means that researchers do not need to duplicate the work of collecting data on millions of packages. The easier we make adoption, the more time and effort we save them.

Identifying OSS used in scientific research

It is difficult to trace the dependency relationship between a scientific paper and the software used in its research. We plan to augment our data to identify the packages most critical to scientific research.
Resources: ecosyste.ms website

Declarative external dependencies in Rust

Improving security in the Rust package management ecosystem by declaratively recording non-Rust dependencies.
Fund
Funded 0 USD (0 GBP)
Goal (163,066 GBP) 214,560 USD

Because there is no way to declaratively record a Rust package’s dependency on a non-Rust package, CVEs from these external dependencies are not easily identifiable from the Rust ecosystem. This means that some vulnerabilities cannot be detected or mitigated, and that developers have incomplete information on their dependency graphs.

Rust’s build.rs is used to build and link to external dependencies. But this strategy involves executing arbitrary code, which poses problems: it makes dependency graph discovery and security review difficult; and it creates a vector for build-time vulnerabilities in dependants of packages that use build.rs.

We propose creating a specification for a declarative build.toml file that allows Rust developers to specify their external dependencies without being subject to the aforementioned security and discoverability problems.

To aid community adoption, we plan to additionally create a Rust dependency graph visualisation tool that will allow developers to understand their dependencies in depth.

Open Infrastructure Observatory

Empowering users, funders and researchers to identify critical Open Source projects at risk of being unmaintained.
Fund
Funded 0 GBP
Goal 133,000 GBP

We are currently building the components of an observatory that allows users to identify and monitor the world’s critical Open Source packages in real time.

A public observatory would inform users and companies when dependencies become insecure or unmaintained. It would allow funders to intelligently allocate money to the most critical projects. And it would empower researchers, governments and foundations to understand how Open Source software underpins our global tech infrastructure.

We are doing this work in a piecemeal fashion, starting with the features listed here. We are looking for funding to develop the broader project as a public-benefit resource.

Components

Unveiling Binary Dependencies

Many packages depend on binaries, but this dependency relationship is hidden and cannot be recorded by package managers.

Connecting Repackaged Packages

CVEs are filed against a canonical package like pypi/pip, but repackaged versions (eg in Homebrew or Nix) lose this security information.

Identifying Bernies

Critical packages can covertly become Bernies — packages that appear maintained but are really abandoned.

Tracking Patches

Many packages are augmented by system package managers' patches. However, the security implications of these patches are not currently tracked.

NYU Software Supply Chain Security Operations Center

Training the next generation of software supply chain security experts.
Fund
Funded 50,000 USD (38,000 GBP)
Goal (76,000 GBP) 100,000 USD

NSOC is a new software supply chain security research lab embedded within NYU. Our supervisors mentor a cohort of postgraduate students and guide them towards making impactful and respectful contributions towards the security of specific Open Source ecosystems.

NSOC's pillars

Connect

Students serve as dedicated liaisons to specific Open Source ecosystems. Before engaging as security researchers, each student undergoes structured onboarding in the norms and culture of their ecosystem.

Inspect

Students develop and extend fuzzing frameworks, LLM-assisted code review pipelines, and automated patch generation agents.

Detect

Continuous monitoring powered by ecosyste.ms, covering dependency changes, anomalous package behavior, suspicious injections, and unmaintained critical components. NSOC coordinates responsible disclosure through ecosystem liaisons.

Direct

Annual ecosystem report cards assess security posture across trusted publishing adoption, dependency hygiene, and vulnerability responsiveness. NSOC delivers direct code integrations and coordinates with OpenSSF, NIST, and ecosystem governance bodies.
Resources: NSOC website

Have questions?

Get in touch