Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-06 00:34 UTC

middag-io / middag-php-framework

MIDDAG PHP Framework — Kernel, Container, Inertia adapter, Middleware, Router, and Domain abstractions for Moodle, WordPress, and custom hosts.

PHPApache-2.0★ 0 stars⑂ 0 forkssince Jun 2026View on GitHub ↗

middag-io/middag-php-framework holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (84/100) and lowest on Community & Adoption (44/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

MIDDAGOrganization
0 followers13 public repossince Apr 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistmiddag-io/frameworkv1.18.11,668403 days agocontainerframeworkwordpressrouterstandalonedddmoodlekernelinertiapsr-15form-engine

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
6.9/36Commit cadence10/52 weeks with commits
18/18Commit volume250 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year250
human_commit_share0.79
days_since_last_push3
active_weeks_last_year10

Release discipline

100Exceptional
How it's scored
27/27Ships releases40 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~4.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count40
latest_release_tagv1.18.1
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases4.3
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?

44Weak · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
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 (Apache-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_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
43/80Monthly downloads1,668 downloads/month across packagist
4/20Registry dependents3 packages depend on it
Inputs used
packagesmiddag-io/framework
dependents3
ecosystemspackagist
total_downloads6,789
monthly_downloads1,668
unverified_packages_excluded

Sustainability & Governance

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

54Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.1/22.5Commit distributiontop contributor authored 100% of commits
2.7/13.5Contributor breadth2 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.995
How it's scored
36.8/42Issue resolution88% of issues closed
29.6/30PR acceptance82/83 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/10 approved changesets -- score normalized to 0
Inputs used
merged_prs82
open_issues1
closed_issues7
prs_merged_7d1
prs_decided_7d1
prs_merged_30d8
prs_decided_30d8
issue_closed_ratio0.875
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
0/25Owner reach0 followers of middag-io
9.2/25Track record13 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginmiddag-io
public_repos13
account_age_days154

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 3 days ago
20/20Version history40 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmiddag-io/framework
ecosystemspackagist
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests10 out of 17 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.middag.dev
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsclient-middag, platform-php, type-library, status-active
has_wikiyes
homepagehttps://docs.middag.dev
docs_sitehttps://docs.middag.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

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
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.2/2.5CI-Tests10 out of 17 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/10 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5
Excluded from scoring (no data or not applicable): 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.

57Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history79 of 79 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes9,731
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
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
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
55/55Manageable file sizes0/529 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes38,709
source_files_sampled529
oversized_source_files0

Key facts

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

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

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-06 00:34 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests10 out of 17 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/10 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 29
RegistryPackageVersion constraintManifest
Packagistmiddag-io/ui^1.3composer.json
Packagistmonolog/monolog^3.0composer.json
Packagistnyholm/psr7^1.8composer.json
Packagistpsr/clock^1.0composer.json
Packagistpsr/container^2.0composer.json
Packagistpsr/http-client^1.0composer.json
Packagistpsr/http-factory^1.0composer.json
Packagistpsr/http-message^1.0 || ^2.0composer.json
Packagistpsr/http-server-handler^1.0composer.json
Packagistpsr/http-server-middleware^1.0composer.json
Packagistpsr/log^3.0composer.json
Packagistpsr/simple-cache^2.0 || ^3.0composer.json
Packagistsymfony/cache^7.0 || ^8.0composer.json
Packagistsymfony/clock^7.0 || ^8.0composer.json
Packagistsymfony/dependency-injection^7.0 || ^8.0composer.json
Packagistsymfony/deprecation-contracts^3.7composer.json
Packagistsymfony/event-dispatcher-contracts^3.0composer.json
Packagistsymfony/http-client^7.0 || ^8.0composer.json
Packagistsymfony/http-foundation^7.0 || ^8.0composer.json
Packagistsymfony/http-kernel^7.0 || ^8.0composer.json
Packagistsymfony/messenger^7.0 || ^8.0composer.json
Packagistsymfony/property-access^7.0 || ^8.0composer.json
Packagistsymfony/property-info^7.0 || ^8.0composer.json
Packagistsymfony/psr-http-message-bridge^7.0 || ^8.0composer.json
Packagistsymfony/routing^7.0 || ^8.0composer.json
Packagistsymfony/serializer^7.0 || ^8.0composer.json
Packagistsymfony/translation-contracts^3.0composer.json
Packagistsymfony/uid^7.0 || ^8.0composer.json
Packagistsymfony/validator^7.0 || ^8.0composer.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.