24.6 Accessing Resources and Support¶

Maintaining open source software is often unpaid work with high expectations. Yet critical infrastructure depends on projects maintained by individuals or small teams with limited resources. The good news is that the ecosystem increasingly recognizes this unsustainability—and resources exist to help. Funding programs, security tools, mentorship networks, and foundation support can provide maintainers with help they need to improve security without bearing all costs themselves.

Many maintainers don't know these resources exist, or assume they're only for large projects. In reality, programs range from automated tools anyone can use to significant funding for critical projects to community mentorship open to all. This section catalogs available resources and provides guidance on accessing them.

OpenSSF Programs¶

The Open Source Security Foundation (OpenSSF)² coordinates industry efforts to improve open source security. Several programs directly support maintainers.

OpenSSF program descriptions and eligibility:

Alpha-Omega Project:

Alpha-Omega provides funding and security expertise to improve security of critical open source projects.

In 2024, Alpha-Omega distributed nearly $6 million in grants to critical projects.¹ Supported projects include Python Software Foundation (dedicated security positions), OpenJS Foundation (Node.js and broader JavaScript ecosystem security), Ruby Central (RubyGems security), FreeBSD Foundation, Rust Foundation, Linux kernel, and Homebrew. The program helps staff security teams at major organizations and funds ecosystem-wide initiatives like malicious package detection, security audits, and infrastructure hardening.

Scorecard:

Scorecard³ automatically assesses open source project security practices and provides actionable improvement suggestions.

# .github/workflows/scorecard.yml
name: Scorecard analysis
on:
  schedule:

    - cron: '0 6 * * 0'  # Weekly

  push:
    branches: [ main ]

jobs:
  analysis:
    runs-on: ubuntu-latest
    steps:

      - uses: ossf/scorecard-action@v2

        with:
          results_file: results.sarif
          publish_results: true

Scorecard results help you identify and prioritize security improvements. Many organizations use Scorecard ratings when evaluating dependencies.

Allstar:

Allstar⁴ automatically enforces security best practices on GitHub repositories.

Allstar is particularly useful for organizations managing multiple repositories, ensuring consistent security configuration.

Other OpenSSF resources:

• OpenSSF Best Practices Badge⁵: Self-certification showing your project follows security best practices
• Package Analysis⁶: Automated analysis of packages for malicious behavior
• Security Insights⁷: Standard format for publishing security information
• OpenSSF Training⁸: Free security training courses

Internship and New Contributor Programs¶

Mentorship and internship programs provide projects with contributors while giving participants meaningful experience.

GSoC and mentorship opportunities:

Google Summer of Code (GSoC)⁹:

How to participate as a mentoring organization:

1. Apply during the organization application period
2. Propose specific project ideas, including security improvements
3. Identify mentors willing to guide contributors
4. If accepted, review and select contributor applications
5. Mentor contributors through the program

Linux Foundation Mentorship:

Other student and early-career programs:

• Outreachy¹¹: Internships for underrepresented groups in tech
• MLH Fellowship¹²: Programs that can include open source contribution
• University partnerships: Many universities seek capstone projects; security improvements make good projects

Sovereign Tech Funds¶

Government-backed funds increasingly recognize open source as critical infrastructure and provide direct funding.

Sovereign tech fund overview:

Sovereign Tech Fund (Germany):

The Sovereign Tech Fund (STF)¹³ is a German government-backed program, operated by the Sovereign Tech Agency, funding open digital base technologies.

STF has funded security work on projects including curl, OpenSSL, and numerous others. Funding can cover maintainer time, security audits, infrastructure costs.

Other government programs:

Application guidance:

Government funds typically want:

• Clear description of the project and its importance
• Specific work plan with deliverables
• Budget justification
• Explanation of public benefit
• Maintenance plan beyond the grant period

Security improvements (audits, fixing vulnerabilities, implementing security features) align well with fund objectives.

Corporate Sponsorship and Support¶

Many companies that depend on open source provide funding and support to projects they use.

Corporate sponsorship landscape:

GitHub Sponsors:

Open Collective:

Corporate and ecosystem funding programs:

Many companies with Open Source Program Offices (OSPOs) directly fund projects, and specialized platforms route money to maintainers:

How to attract corporate sponsorship:

1. Make it easy: Enable GitHub Sponsors, Open Collective, or similar
2. Be visible: Clear documentation of who maintains the project
3. Show impact: Download counts, dependent projects, users
4. Communicate needs: Blog about what funding would enable
5. Offer recognition: Sponsor logos in README, website

Maintainers who enable sponsorship mechanisms and communicate their funding needs often find that corporate sponsorships increase. Companies want to support projects they depend on—they just need to know how.

Foundation Resources¶

Software foundations provide infrastructure, legal protection, and support for member projects.

Foundation support (Apache, Linux Foundation, etc.):

Apache Software Foundation (ASF):

Linux Foundation:

Eclipse Foundation:

Other foundations:

• Python Software Foundation (PSF): Supports Python ecosystem
• OpenJS Foundation: JavaScript ecosystem projects
• Rust Foundation: Rust language and ecosystem
• FreeBSD Foundation: FreeBSD and related projects

Benefits of foundation membership:

• Infrastructure (hosting, CI/CD, mirrors)
• Legal protection (trademark, liability)
• Governance frameworks
• Visibility and credibility
• Security resources and coordination
• Funding opportunities

Considerations:

• Foundations have governance requirements
• Project may need to transfer trademarks
• Decisions may require community consensus processes
• Not all projects fit foundation models

Community Support Networks and Mentorship¶

Beyond formal programs, community networks provide peer support, mentorship, and knowledge sharing.

Community mentorship programs:

Informal mentorship:

• Connect with experienced maintainers in your ecosystem
• Join maintainer-focused communities and events
• Ask for advice in community channels
• Offer to mentor others once you have experience

Where to find community support:

Sustainability-focused communities:

• Sustain Podcast¹⁹: Interviews about open source sustainability
• Open Source Collective²⁰: Community around OSC-hosted projects
• LFX Mentorship²¹: Linux Foundation mentorship and funding platform

Security-specific support:

• OpenSSF Slack²²: Community discussions on security
• OWASP Chapters²³: Local security communities
• Security conference communities: Connections made at security events

Application and Eligibility Guidance¶

Navigating funding and support programs can be confusing. Here's general guidance:

For small projects seeking initial support:

1. Enable GitHub Sponsors and/or Open Collective
2. Run Scorecard and work toward passing badge criteria
3. Apply to relevant ecosystem-specific programs
4. Participate in community events to build visibility

For critical infrastructure projects seeking significant support:

1. Document your project's importance (users, dependents, infrastructure role)
2. Apply to Alpha-Omega or similar critical infrastructure programs
3. Apply to Sovereign Tech Fund or NLnet
4. Engage with foundations relevant to your ecosystem
5. Pursue corporate partnerships with companies that depend on your project

Application tips:

• Be specific: Vague requests get vague responses
• Show impact: Numbers, users, dependent projects
• Describe what you'll do: Specific deliverables and timelines
• Explain sustainability: How will work continue after funding ends?
• Follow up: Applications sometimes need persistent follow-up

What funders want to see:

Recommendations¶

We recommend the following approaches to accessing resources and support:

1. Start with free tools: Scorecard, Allstar, and OpenSSF training require no application—just use them to improve your project's security.

2. Enable sponsorship mechanisms: GitHub Sponsors and Open Collective make it easy for users and companies to support you. You might be surprised who contributes.

3. Apply to relevant programs: Don't assume you're not eligible. Programs like Sovereign Tech Fund specifically want to support maintainers, not just large projects.

4. Join foundation communities: Even if your project isn't a member, foundation communities provide valuable connections and resources.

5. Document your project's impact: Numbers help make the case for support. Track downloads, dependents, and users.

6. Connect with peers: Other maintainers face similar challenges and can share what's worked for them. Community support is valuable beyond funding.

7. Be persistent: Many programs have rolling applications or multiple cycles. If you're not accepted initially, improve and reapply.

8. Give back when you can: As you receive support, help others. Mentor new maintainers, contribute to ecosystem security initiatives, share what you've learned.

Resources exist because the industry recognizes that open source sustainability matters. You don't have to maintain critical infrastructure alone and unfunded. Accessing available support improves your project's security, your personal sustainability, and the health of the open source ecosystem.