# Who Maintains the cloudflare/computer Project?

> Discover who maintains the cloudflare/computer project. Learn about the Cloudflare engineering team and approved collaborators governing the repository.

- Repository: [Cloudflare/computer](https://github.com/cloudflare/computer)
- Tags: getting-started
- Published: 2026-08-09

---

**The cloudflare/computer repository is maintained by the Cloudflare engineering team and approved collaborators who have write access, governed by the official collaborator guidelines defined in [`COLLABORATORS.md`](https://github.com/cloudflare/computer/blob/main/COLLABORATORS.md).**

The cloudflare/computer project operates under a structured maintenance model that restricts direct write access to authorized personnel. Understanding who maintains cloudflare/computer is critical for contributors navigating the codebase, as the project enforces specific criteria for participation and code integration.

## The Core Maintainer Team

### Cloudflare Engineering Staff

The primary maintainers are Cloudflare employees with direct write access to the repository. According to the source documentation in [`COLLABORATORS.md`](https://github.com/cloudflare/computer/blob/main/COLLABORATORS.md), the Cloudflare Computer team retains authority over all decisions regarding code changes, release processes, and commit conventions 【/cache/repos/github.com/cloudflare/computer/main/COLLABORATORS.md#L1-L6】.

### Approved External Collaborators

The project also incorporates approved external collaborators who have been granted pull-request access. The [`COLLABORATORS.md`](https://github.com/cloudflare/computer/blob/main/COLLABORATORS.md) file explicitly defines the project as open to "approved collaborators with pull-request access," establishing a tiered permission structure beyond core employees 【/cache/repos/github.com/cloudflare/computer/main/COLLABORATORS.md#L3-L5】.

## Governance and Contribution Policies

### The Collaborator Guide

The [`COLLABORATORS.md`](https://github.com/cloudflare/computer/blob/main/COLLABORATORS.md) file serves as the definitive governance document for repository maintenance. It outlines the workflow privileges and responsibilities expected of maintainers, ensuring centralized control over the project's technical direction.

### Contribution Restrictions

The [`CONTRIBUTING.md`](https://github.com/cloudflare/computer/blob/main/CONTRIBUTING.md) file reinforces maintainer authority by specifying that pull requests should originate from approved collaborators. As implemented in the repository guidelines, maintainers reserve the right to close external contributions that do not meet the established criteria 【/cache/repos/github.com/cloudflare/computer/main/CONTRIBUTING.md#L18-L27】.

## Maintainer Workflow and Repository Setup

Maintainers follow a standardized workflow when working with the cloudflare/computer codebase. The project requires **Node.js 22+** and utilizes npm workspaces for dependency management across packages.

```bash

# Clone the repo (maintainers typically have write access)

git clone https://github.com/cloudflare/computer.git
cd computer

# Install dependencies (Node 22+, npm workspace)

npm install

# Run the full test suite (maintainers verify changes before merging)

npm test

```

## Locating Current Maintainer Information

While the governance structure is documented in policy files, the current roster of maintainers can be identified through several repository locations:

- **GitHub Collaborators Settings**: The definitive source listing individuals with write access
- **Package Documentation**: Individual `packages/*/README.md` files list specific maintainers responsible for each sub-package
- **GitHub Workflows**: The `.github/` directory contains CI/CD pipelines managed exclusively by the maintainer team

## Summary

- The cloudflare/computer project is maintained by the Cloudflare engineering team and approved external collaborators with explicit write access.
- Governance is centralized in [`COLLABORATORS.md`](https://github.com/cloudflare/computer/blob/main/COLLABORATORS.md), which defines privileges for approved collaborators with pull-request access.
- The [`CONTRIBUTING.md`](https://github.com/cloudflare/computer/blob/main/CONTRIBUTING.md) policy restricts contributions to approved collaborators and authorizes maintainers to close non-compliant external submissions.
- Current maintainers are identifiable through GitHub's collaborators interface and individual package README files.

## Frequently Asked Questions

### How can external contributors participate in the cloudflare/computer project?

External contributors must first obtain status as an approved collaborator with pull-request access. The project does not accept unsolicited pull requests from the general public; maintainers may close contributions that do not originate from approved collaborators.

### Where is the official list of cloudflare/computer maintainers documented?

The governance structure is defined in [`COLLABORATORS.md`](https://github.com/cloudflare/computer/blob/main/COLLABORATORS.md) at the repository root, while the current roster of individuals with write access is visible on the GitHub repository's collaborators settings page. Specific package maintainers are listed in their respective `packages/*/README.md` files.

### What distinguishes a maintainer from a regular contributor in cloudflare/computer?

A contributor proposes changes through pull requests, while a maintainer possesses write access to merge code, manage releases, and enforce commit conventions. Only individuals explicitly granted collaborator status in the repository's access controls function as maintainers.

### Can I submit a pull request to cloudflare/computer without being an approved collaborator?

According to the [`CONTRIBUTING.md`](https://github.com/cloudflare/computer/blob/main/CONTRIBUTING.md) guidelines, pull requests should come from approved collaborators only. While the repository code is open-source, external submissions that do not meet the collaborator criteria may be closed by the maintainer team without review.