Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-12 22:37 UTC

containers / podman-compose

a script to run docker-compose.yml using podman

PythonGPL-2.0★ 6,186 stars⑂ 616 forkssince Mar 2019View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

containers/podman-compose holds a health index of 97 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (94/100) and lowest on AI Readiness (64/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

97
overall / 100
Exceptional

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

97
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 85 is calibrated to 97 on the published index scale (record calibration 2026-08-02).

Ownership

ContainersOrganization
6,477 followers107 public repossince Nov 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpodman-compose1.6.0423,1521770 days agopodmanpodman-compose

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

91Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
31.2/36Commit cadence45/52 weeks with commits
18/18Commit volume262 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year262
human_commit_share0.97
days_since_last_push1
active_weeks_last_year45
How it's scored
27/27Ships releases7 releases published
36/36Release recencylatest release 70 days ago
12.6/27Release cadencea release every ~129.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count7
latest_release_tagv1.6.0
releases_from_tagsno
days_since_latest_release70
mean_days_between_releases129.2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

92Excellent · 17% of overall
How it's scored
60/60Stars6,186 stars
23.2/25Forks616 forks
9/15Watchers43 watchers
Inputs used
forks616
stars6,186
watchers43
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com
has_pull_request_templateyes
How it's scored
75/80Monthly downloads423,152 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespodman-compose
dependents
ecosystemspypi
total_downloads
monthly_downloads423,152
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

83Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.7/22.5Commit distributiontop contributor authored 35% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 64 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.348
How it's scored
27.1/42Issue resolution64% of issues closed
22.6/30PR acceptance458/607 decided PRs merged
10.6/13Newcomer PR acceptance9/11 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs458
open_issues300
closed_issues546
prs_merged_7d6
prs_decided_7d6
prs_merged_30d21
prs_decided_30d24
issue_closed_ratio0.645
closed_unmerged_prs149
first_time_authors_30d9
first_time_prs_merged_30d9
first_time_prs_decided_30d11
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach6,477 followers of containers
25/25Track record107 public repos, account ~12 yr old
Inputs used
followers6,477
owner_typeOrganization
is_verified
owner_logincontainers
public_repos107
account_age_days4,661
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 70 days ago
20/20Version history17 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespodman-compose
ecosystemspypi
any_deprecatedno
min_days_since_publish70

Engineering Quality

Are baseline engineering and documentation practices in place?

94Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.json, .pylintrc
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicspodman, docker-compose, linux-containers, rootless-containers
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 64 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
1.5/7.5Vulnerabilities8 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:podman-compose@1.6.0 runtime dependency closure — what installing the published package pulls in — 2 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

64Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history74 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.763
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.json, .pylintrc
11/11Static type checkingexamples/nodeproj/jsconfig.json
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsexamples/nodeproj/jsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.03
How it's scored
27/45Type-checkable codePython with type-check config (examples/nodeproj/jsconfig.json)
54.7/55Manageable file sizes1/182 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes207,934
source_files_sampled182
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample, examples
Inputs used
example_dirsexample, examples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

6,186GitHub stars
99contributors
262commits, last 12 months
1days since last push
7releases
2bus factor
300open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 616 ⇿
0Stars
616Forks
7Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

012525037550062561372019-052022-122026-08
Major 0Minor 6Patch 1

Each point covers 7 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-12 22:36 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 64 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
2Vulnerabilities8 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
PyPIpython-dotenvpyproject.toml
PyPIpyyamlpyproject.toml
All dependencies 47

Full resolved dependency set from the GitHub dependency graph: 4 direct and 43 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIpython-dotenvdirect
PyPIpython-dotenv1.0.1direct
PyPIpyyamldirect
PyPIpyyaml6.0.1direct
npmexpress~4.16.4indirect
npmnodemon^2.0.14indirect
npmredis^3.1.2indirect
PyPIaiohttpindirect
PyPIaioredisindirect
PyPIapscheduler3.11.2indirect
PyPIastroid3.1.0indirect
PyPIcachetools5.3.3indirect
PyPIcertifi2025.11.12indirect
PyPIcffi2.0.0indirect
PyPIchardet5.2.0indirect
PyPIcharset-normalizer3.4.4indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.4.3indirect
PyPIcryptography50.0.0indirect
PyPIdill0.3.8indirect
PyPIdistlib0.3.8indirect
PyPIfilelock3.13.1indirect
PyPIidna3.15indirect
PyPIiniconfig2.0.0indirect
PyPIisort5.13.2indirect
PyPImccabe0.7.0indirect
PyPImypy1.15.0indirect
PyPImypy-extensions1.1.0indirect
PyPIpackaging23.2indirect
PyPIparameterized0.9.0indirect
PyPIplatformdirs4.2.0indirect
PyPIpluggy1.4.0indirect
PyPIpycparser2.23indirect
PyPIpylint3.1.0indirect
PyPIpyproject-api1.6.1indirect
PyPIpytest8.0.2indirect
PyPIrequests2.32.5indirect
PyPIruff0.14.8indirect
PyPItomlkit0.12.4indirect
PyPItox4.13.0indirect
PyPItypes-pyyaml6.0.12.20250402indirect
PyPItypes-requests2.32.0.20250328indirect
PyPItypes-setuptools80.7.0.20250516indirect
PyPItyping-extensions4.13.2indirect
PyPItzlocal5.3.1indirect
PyPIurllib32.6.3indirect
PyPIvirtualenv20.26.6indirect
Dependency advisories 0

Installing pypi:podman-compose@1.6.0 pulls in 2 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.