ruphy/publiccode.yml — explained in plain English
Analysis updated 2026-07-16 · repo last pushed 2018-06-26
A city builds a pothole-reporting app and adds a publiccode.yml file so other cities can discover and reuse it.
Government IT staff search a catalog of publiccode.yml files to find existing software instead of building from scratch.
A policy team evaluates whether a tool built by another administration fits their national legal framework by reading its publiccode.yml.
A scanner crawls public code repositories for publiccode.yml files and publishes the results as open data for anyone to browse.
| ruphy/publiccode.yml | chrisor-dev/claude-autosync | dangerousyams/muxer | |
|---|---|---|---|
| Stars | 3 | 2 | 2 |
| Language | Shell | Shell | Shell |
| Last pushed | 2018-06-26 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 1/5 | 3/5 | 3/5 |
| Audience | pm founder | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
No setup required, it is a file format standard, so you just create a YAML file following the spec.
The publiccode.yml standard is a simple way for government agencies to describe the software they build, so that other agencies can actually find and reuse it. The idea is that lots of public administrations create useful software tools, but hardly anyone else knows these tools exist or whether they'd work in a different city or country. The project defines a standard file, literally called publiccode.yml, that sits inside a software project and describes it in a consistent way. The file includes things like the project title and description, who built it, what stage of development it's in, who handles maintenance, and what legal or technical requirements it has. The format is meant to be readable by both humans and computers, so a civil servant could open it and understand what the software does, while a search tool could scan it automatically. This would be useful for government IT staff, policy teams, or anyone working in public administration who wants to avoid building a solution from scratch. If one city builds an app for reporting potholes and documents it with this standard, another city could find it and evaluate whether the same approach would work for them. The file captures details that matter for government contexts specifically, like which national legal frameworks the software supports, that you wouldn't find in a typical open-source project's README. The project is still in early development (alpha status) at version 0.1, and was created by the Italian Digital Transformation Team. There's also a related effort to build a scanner that crawls public websites looking for these files and publishes what it finds as open data, making the whole ecosystem more discoverable.
A standard file format that government agencies put inside their software projects so other agencies can find and reuse their tools. It captures details like who built it, maintenance status, and legal frameworks it supports.
Mainly Shell. The stack also includes Shell, YAML.
Dormant — no commits in 2+ years (last push 2018-06-26).
The explanation does not mention a license, so it is unclear what permissions apply to using this project.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Verify against the repo before relying on details.