Projects using projectfile
This page lists what consumes projectfile documents in some capacity — as a metadata source, a CI convention layer, or an integration target. It is not exhaustive; inclusion here does not imply endorsement or an official relationship with the projectfile specification.
Tools recorded in the registry
Section titled “Tools recorded in the registry”The specification repository’s extension registry records, per namespace, which tools produce it and which consume it. That record is rendered directly, so the table below changes when a registry pull request lands rather than when someone remembers to edit this page.
| Tool | Namespaces |
|---|---|
| bridge (pf-bridge) | org.projectfile.artifacts (reads) |
| ignorelint | org.ignorelint (reads) |
| pf-ci (pf-ci) | org.projectfile.artifacts (reads), org.projectfile.events (writes) |
| projectfile-cli | org.packagist.composer (reads), org.projectfile.cli (writes), org.projectfile.codeowners (reads), org.projectfile.editors (reads), org.projectfile.readme (reads), org.python.pep621 (reads) |
| spiderlint | org.spiderlint (reads) |
5 tools across 41 namespaces.
Documents you can read in full
Section titled “Documents you can read in full”Every project below is public and publishes its document, so you can see what a
real one looks like before writing your own. The ones carrying
org.projectfile.ci have their whole CI pipeline generated from the document.
This list is curated by hand — every row was checked by opening the document on its forge — so it grows one pull request at a time rather than from a scan of the fleet. The registry table above is generated from the specification’s own record; this one is not.
| Project | Relation | Document |
|---|---|---|
| The Projectfile Specification | The specification and its own document | projectfile.yaml |
| Projectfile CLI | pf-cli — reads, writes and validates the document |
projectfile.yaml |
| Projectfile Bridges | pf-bridge — projects the document onto files and forges |
projectfile.yaml |
| Projectfile CI Resolver | pf-ci — lowers org.projectfile.ci to workflow YAML |
projectfile.yaml |
| Projectfile Core | The Go library the tools are a thin CLI over | projectfile.yaml |
| M6E core · container · b19 · library | The Makefile framework that consumes org.projectfile.ci: it turns the service DAG into the lint, build and publish targets a project runs |
projectfile.yaml and three siblings |
| B19 / Ubuntu | Base image; its pipeline is generated from the document | projectfile.yaml |
| Ignorelint | Linter for ignore files; reads org.ignorelint |
projectfile.yaml |
Third-party adopters
Section titled “Third-party adopters”No third-party adopters are listed yet. If you use a projectfile document in your project, in a tool, or in a registry, you can be recorded here two ways:
- Register your extension namespace — if you ship tooling against a
namespace you control, add it to the non-normative registry. An entry with a
linkslist naming your tool as a consumer or producer is what puts you in the table above. See §6.5. - Open a pull request against this site — add a row to the table above with
a link to your public document, exactly as the existing rows do. A public
projectfile.yamlis the only requirement; a project with no reachable document cannot be listed.
Both paths are pull requests with a one-line rationale. There is no gate-keeping, and inclusion is not an endorsement.