Español · Українська

The Projectfile Specification

Stack- and vendor-agnostic software project specification file.


Why this exists

I hate multitude of files in the roots of my projects, so I decided to add another one to rule them all.

What it does

Projectfile specification describes "projectfile", simple hierarchical file "about project". Can be YAML, TOML or JSON. There is a CLI tool that hides formats from you, reads and writes keys and supports includes, interpolation and other interesting stuff.

Good fit

• You want to have a single source of truth for your tooling
• You like the idea of deterministic generation of 10+ various things from one thing
• You have fleet of projects with complex stacks
• You have more than one developer workflow
• You use CI/CD
• You have OCD

Building

Run make with no arguments for the default target; run make help to list every target.

Pipeline entry points:

• make analyze — Run the heavy analysis sweep (mutation testing, benchmarks)
• make audited — Re-scan the pinned dependencies and published artifacts for new vulnerabilities
• make check-outdated — Report every pinned dependency that lags upstream
• make ready-to-publish — Run the pseudo-CI pipeline locally — build, test and scan, without publishing

What’s next

• bullying people to force them to abandon separate config files for their developement tools

Policies

• How to contribute
• Security policy
• Getting support
• Code of Conduct
• AI and LLM Policy

Links

• Projectfile Specification

License

This project is licensed under MIT OR CC-BY-4.0 — see the LICENSE file for details.