Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-04 15:14 UTC

beluga-php / docker-php-api

Docker API generated files from OpenAPI Specification

PHPMIT★ 3 stars⑂ 9 forkssince Dec 2020forkView on GitHub ↗

beluga-php/docker-php-api holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (64/100) and lowest on Engineering Quality (28/100). It was last updated today. 2 contributors account for most of its recent work.

47
overall / 100
Weak

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.

47
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 48 is calibrated to 47 on the published index scale (record calibration 2026-08-02).

Ownership

beluga-phpOrganization
2 followers2 public repossince Dec 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistbeluga-php/docker-php-apiv7.1.45.552,309500 days ago

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
3/10OpenSSF Scorecard: Maintained0 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year1
human_commit_share0.97
days_since_last_push0
active_weeks_last_year1
How it's scored
27/27Ships releases26 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~97.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count26
latest_release_tagv7.1.45.5
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases97.6
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?

31At Risk · 17% of overall
How it's scored
4.9/60Stars3 stars
7.5/25Forks9 forks
1.7/15Watchers3 watchers
Inputs used
forks9
stars3
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
62.9/80Monthly downloads52,309 downloads/month across packagist
4/20Registry dependents3 packages depend on it
Inputs used
packagesbeluga-php/docker-php-api
dependents3
ecosystemspackagist
total_downloads593,730
monthly_downloads52,309
unverified_packages_excluded

Sustainability & Governance

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

64Moderate · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
13.5/22.5Commit distributiontop contributor authored 40% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 14 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.4
How it's scored
36.8/42Issue resolution88% of issues closed
19.3/30PR acceptance9/14 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 6/23 approved changesets -- score normalized to 2
Inputs used
merged_prs9
open_issues1
closed_issues7
prs_merged_7d0
prs_decided_7d3
prs_merged_30d0
prs_decided_30d3
issue_closed_ratio0.875
closed_unmerged_prs5
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
3.4/25Owner reach2 followers of beluga-php
14.9/25Track record2 public repos, account ~5 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_loginbeluga-php
public_repos2
account_age_days2,091

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 0 days ago
20/20Version history50 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbeluga-php/docker-php-api
ecosystemspackagist
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

28At Risk · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config.php-cs-fixer.php
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

10Critical
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsdocker-engine-api, open-api, php, hacktoberfest
has_wikino
homepage
docs_site
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 6/23 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 14 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained0 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0.8/40Legible commit history1 of 65 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.015
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.php-cs-fixer.php
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 67
8/8Automated maintenance2 of the last 67 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.03
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
54.9/55Manageable file sizes2/783 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes116,173
source_files_sampled783
oversized_source_files2

Key facts

3GitHub stars
5contributors
1commits, last 12 months
0days since last push
26releases
2bus factor
1open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
15Releases

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.

0246810912021-112023-122025-12
Major 0Minor 0Patch 0

Each point covers 4 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-09-04 15:14 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/23 approved changesets -- score normalized to 2
10Contributorsproject has 14 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained0 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
Packagistjane-php/json-schema-runtime^7.5composer.json
Packagistjane-php/open-api-runtime^7.5composer.json
Packagistpsr/http-client^1.0composer.json
Packagistpsr/http-client-implementation*composer.json
Packagistpsr/http-factory^1.0composer.json
Packagistpsr/http-factory-implementation*composer.json
Packagistpsr/http-message^2.0composer.json
Packagistpsr/http-message-implementation*composer.json
Packagistsymfony/deprecation-contracts^3.3composer.json
Packagistsymfony/options-resolver^6.3 || ^7.0composer.json
Packagistsymfony/serializer^6.3 || ^7.0composer.json
Packagistsymfony/validator^6.3 || ^7.0composer.json
All dependencies 21

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

RegistryPackageVersionRelation
Packagistjane-php/json-schema-runtimedirect
Packagistjane-php/open-api-runtimedirect
Packagistpsr/http-clientdirect
Packagistpsr/http-client-implementationdirect
Packagistpsr/http-factorydirect
Packagistpsr/http-factory-implementationdirect
Packagistpsr/http-messagedirect
Packagistpsr/http-message-implementationdirect
Packagistsymfony/deprecation-contractsdirect
Packagistsymfony/options-resolverdirect
Packagistsymfony/serializerdirect
Packagistsymfony/validatordirect
Packagistergebnis/composer-normalizeindirect
Packagistext-mbstringindirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistjane-php/open-api-3indirect
Packagistphpindirect
Packagistphp-http/client-commonindirect
Packagistphp-http/discoveryindirect
Packagistphp-http/multipart-stream-builderindirect
Packagistroave/security-advisoriesindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.34.0 — full methodology · metrics wiki.

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