repo-info: A Perl Toolkit for Auditing Docker Official Image Licenses and Layers
Extended information (especially license and layer details) about the published Official Images
At a glance
- What is it?
- docker-library/repo-info is a set of Perl scripts that generate extended reports on Docker Official Images, focusing on license and layer metadata. It is a work-in-progress tool for those who need deeper visibility into official image provenance.
- Who is it for?
- Adopt repo-info if you maintain or rely on Docker Official Images and need a scripted way to audit license and layer metadata beyond what Docker Hub shows. Skip it if you need a polished, user-friendly tool or if you work with non-official images, as it is specifically scoped to the official library.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Perl, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- docker-library/repo-info612 ★ · +6
| Repository | 2026-08-26 | 2026-11-15 |
|---|---|---|
| docker-library/repo-info | 606 | 612 |
6 Stars in the last 81 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What repo-info Actually Does
The repository is a collection of Perl scripts that generate reports of extended information about published official image repositories. The key words are 'extended information'. Docker Hub shows basic metadata like size and tags, but not necessarily the license or detailed layer breakdown. repo-info fills that gap by pulling and organizing that extra data. It is aimed at people who need to audit or document what is inside an official image, such as compliance officers, security engineers, or maintainers of downstream distributions. The README is clear that this is a firm work in progress, so do not expect a finished product.
The Two Scripts and Their Automation
The repository contains at least two scripts: update-remote.sh and scan-local.sh. The README links to automated Jenkins jobs for both. The remote job runs update-remote.sh, which likely fetches data from a remote source, probably the Docker Hub API or the official-images repository. The local job runs scan-local.sh, and the README notes there is one job per repo, meaning it scans each official image repository individually. The data flow is not fully documented, but the split suggests a two-pass approach: first update remote metadata, then scan local images to extract layer details. This is a design choice that separates fetching from processing, which can help with debugging but also adds complexity.
Getting It Running: Commands and Configuration
The README does not include explicit installation instructions, but the scripts are in the repository. To run it, you would clone the repository and execute the scripts with Perl. The scripts are named update-remote.sh and scan-local.sh, so a typical invocation might be './update-remote.sh' or 'perl update-remote.pl', though the exact extension is not specified. There are no documented configuration keys or environment variables. The automated jobs at doi-janky.infosiftr.net are the primary way it runs, so you may need to set up your own CI pipeline to replicate that. Since there are no releases, you would use the master branch as-is. The lack of setup documentation is a real barrier for newcomers.
A Genuine Limitation: Work in Progress with No Releases
The README explicitly states it is a firm work in progress. That is not a marketing line; it is a warning. The latest default-branch commit visible on 7 November 2026 was dated 7 November 2026. The code may change, so pin a specific commit when reproducibility matters and review changes before updating. If you need a reliable tool for production compliance reporting, this may not be ready. Another limitation is scope: it only works with published official image repositories, so if you use community images or your own builds, this tool is useless. The scripts also require a Perl environment and likely access to Docker, but that is not documented. You are on your own for troubleshooting.
Alternative: Using Docker Hub API Directly
A practical alternative is to query the Docker Hub API directly. Docker Hub exposes endpoints for repository metadata, including tags and sometimes layer information. The difference is that repo-info abstracts that into a report, while a direct API approach gives you raw JSON that you can parse with any tool. The trade-off is that the API may not provide license information in a structured way, which is why repo-info exists. Another alternative is to use 'docker inspect' on a pulled image to see layer IDs and sizes, but that does not give license data. So repo-info fills a specific niche, but if you only need layer details, a simple shell script with docker inspect might suffice.
Maintenance and License Implications
The project is licensed under Apache-2.0, which is permissive and allows you to modify and redistribute the scripts, provided you include the license notice. That is a plus for internal use. However, maintenance is a concern. With no releases and an unknown last push, the project may be dormant. The automated jobs at doi-janky.infosiftr.net suggest that the Docker library team uses it internally, so it might be maintained as needed, but there is no public roadmap. You should check the commit history on GitHub to see how active it is. The cost of upgrading is low because it is just scripts, but you must be prepared to read Perl code to fix issues.
Who Should Adopt It and What to Verify First
Adopt repo-info if you are a maintainer of the Docker Official Images or a downstream project that needs to document licenses for compliance. It is also useful for researchers studying image composition. Do not adopt it if you want a polished tool with documentation or if you need support for non-official images. Before using it, verify that the scripts still run with your Perl version and Docker setup. Check the Jenkins jobs to see if they are green. Also, test the output on a single repository to see if the report format meets your needs. The project is small enough that you can fork it and adapt it, but that requires Perl skills.
Editorial conclusion
Adopt repo-info if you maintain or rely on Docker Official Images and need a scripted way to audit license and layer metadata beyond what Docker Hub shows. Skip it if you need a polished, user-friendly tool or if you work with non-official images, as it is specifically scoped to the official library. Before relying on it, verify that the automated jobs are still running and that the output format matches your reporting needs, since the project is explicitly a work in progress with no recent releases or documented stability.
Frequently asked questions
What does docker-library repo-info collect?
Extended information about published Official Images, with licence and layer details named as the speciality. The reports are generated by shell scripts from data held in the `repos/` directory, with `generate-readme.sh` producing the index and `update-remote.sh` and `scan-local.sh` doing the collection work.
How is repo-info run?
Through two automated jobs linked from the README: one for `update-remote.sh`, and one for `scan-local.sh`, which runs a separate job per repository. The collection happens in containers built from four Dockerfiles, and the repository's one Perl file, `.remote.pl`, sits alongside the shell scripts.
Which package managers does repo-info inspect?
The local Dockerfiles are named for three families: `Dockerfile.local-apk`, `Dockerfile.local-dpkg` and `Dockerfile.local-rpm`, covering the apk, dpkg and rpm lineages. A fourth, `Dockerfile.remote`, has no package manager in its name and serves the remote side.
Is repo-info a finished tool?
Not by its own account. The README describes it as still a work in progress and welcomes concrete suggestions about improvement in gathering or presentation. There are no GitHub releases, and the default branch is `master` rather than `main`, so there is no tag to pin against.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/docker-library-repo-info)Star history chart for your README
[](https://hysenlabs.com/projects/docker-library-repo-info)Was this useful?