Open Source Three-Page Mock-up Skip to main content
Design mock-up · Option B: three pages This is a proposed Open Source section in three parts, Impact, Tools and research, and 2025 in review, prepared for Trail of Bits review.

Making open source safer for everyone

Advancing the science of security means sharing the work. We release our tools as open source, contribute fixes to the projects the industry depends on, build signing and provenance infrastructure for package registries, and publish the reports from our public security reviews.

Merged upstream PRs

1,575+

Merged between 2023 and 2025

Upstream projects

90+

Contributed to in 2025

Public audit reports

660

Published in our library

PtP fixes merged

466

Merged as of Oct 16, 2026

Why we do this

Trail of Bits has worked with the open-source community since 2012. We publish almost everything we build, from smart-contract fuzzers to AI-driven bug finders, and our engineers contribute directly to the open-source projects that our clients and the wider industry depend on.

For a maintainer, a bug report is only the first step. Triaging the report, writing a patch and getting it merged takes expertise and time, and our engineers do that work alongside the maintainers.

Securing the world's software starts with helping the people who maintain it.
  • Public release by default

    We publicly release nearly all of our internal and approved client projects, so the tools we use on client engagements are available to everyone.

  • Upstream fixes

    We submit patches along with our bug reports and follow each one through review until it is merged. Between 2023 and 2025 we merged 1,575+ PRs into external projects.

  • Shared infrastructure

    Package registries, signing systems and widely used libraries are dependencies of thousands of other projects, so improving their security also protects those projects.

  • Published audit reports

    When a foundation or sponsor funds a security review of an open-source project, we publish the full report in our library.

Projects we've helped secure

We have contributed patches, published audits, built infrastructure or supported maintainers for each of these open-source projects. Use the domain filters to see the projects in each area.

90+

Projects contributed to in 2025

68

Projects in Patch the Planet

660

Public audit reports

  • Sigstore
  • PyPI
  • Python
  • Homebrew
  • RubyGems
  • vLLM
  • PyTorch
  • Hugging Face
  • ONNX
  • RustCrypto
  • OpenSSL
  • Open Quantum Safe
  • Botan
  • cURL
  • Let's Encrypt
  • LLVM
  • Rust
  • Go
  • Ethereum
  • Solady
  • Zcash
  • Kubernetes
  • Linux
  • NixOS
  • aiohttp
  • urllib3
  • SQLite
  • Samba
  • BIND 9
  • Zeek
  • Suricata
  • Scapy
  • NATS
  • Valkey
  • Keycloak
  • Drupal
  • WordPress
  • PHP
  • Ruby on Rails
  • Symfony
  • Matrix
  • Ladybird
  • SciPy
  • OpenClaw
  • Harbor
  • gem.coop
  • Ansible
  • rsync
  • zlib
  • cryptlib
  • Noble cryptography
  • mlkem-native
  • SecureDrop
  • Jaeger
  • OpenBao
  • GPAC

Our open-source work by domain

Each domain below collects our upstream contributions, public audits, research and released tools for that area of security.

Supply chain

Securing how software is packaged, signed and installed

We build publishing, signing and transparency infrastructure for package ecosystems, including Trusted Publishing and attestations on PyPI, build provenance for Homebrew, and monitoring for Sigstore's transparency log. We also publish audits of package registries such as RubyGems.org and PyPI.

19.5k
PyPI projects on Trusted Publishing
134
Warehouse PRs in 2024
40+
Rekor PRs in 2025
Sigstore
PyPI
Python
Homebrew
RubyGems
Go

Featured story

2023 to 2026 · 7 milestones

Securing Python packaging, end to end

Since 2023 we have worked with the Python Packaging Authority, PyPI and Sigstore on publishing security for Python packages. The work replaced long-lived API tokens with short-lived credentials tied to a CI identity, added signed attestations to published files, and we are now proposing a transparency log for PyPI.

  1. May 2023
    Infrastructure
    Trusted Publishing: a new benchmark for packaging security

    OIDC-based publishing for PyPI replaces long-lived API tokens with short-lived tokens scoped to a CI identity. Google's Open Source Security Team funded this work.

  2. Nov 2024
    Standard
    Attestations: a new generation of signatures on PyPI

    We implemented PEP 740 index-hosted attestations using Sigstore, and they are enabled by default in the official PyPI publish action.

  3. Jan 2025
    Upstream PR
    PyPI now supports archiving projects

    Maintainers can now mark a project as archived to show downstream users that it no longer receives updates. Alpha-Omega funded this work.

  4. Sep 2025
    Research
    Supply chain attacks are exploiting our assumptions

    This post explains the trust assumptions behind package installs and how build provenance and signing address them.

  5. Dec 2025
    Tool
    Catching malicious package releases using a transparency log

    We made rekor-monitor ready for production use, so PyPI and npm maintainers are alerted when their signing identity is misused. OpenSSF funded this work.

  6. Jan 2026
    Infrastructure
    Building cryptographic agility into Sigstore

    We replaced hard-coded algorithms with configurable algorithm suites across Fulcio, Rekor, Cosign and sigstore-go, which prepares Sigstore for post-quantum signing.

  7. 2026
    Standard
    A transparency log for PyPI

    We have written a draft PEP and run a test log that records every PyPI artifact and its publishing identity in a tamper-evident log.

More Supply chain work

Ways to work with us

Patch the Planet

Do you maintain a critical open-source project?

Patch the Planet gives selected maintainers a week of dedicated security engineering, including patches.

Fund or sponsor

Want to fund security work on a project you rely on?

We work with foundations and companies that fund audits and security engineering for open-source projects.