Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 10:59 UTC

alleyinteractive / mantle-framework

Mantle is a framework for building large, robust websites and applications with WordPress. Framework for https://github.com/alleyinteractive/mantle

PHPGPL-2.0★ 28 stars⑂ 7 forkssince Feb 2020View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

alleyinteractive/mantle-framework holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (60/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

88
overall / 100
Excellent

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.

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

Ownership

AlleyOrganization
114 followers273 public repossince May 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistalleyinteractive/mantle-frameworkv1.22.127,47912323 days ago

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
22.2/36Commit cadence — 32/52 weeks with commits
18/18Commit volume — 148 commits in the last year
10/10OpenSSF Scorecard: Maintained — 18 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year148
human_commit_share0.96
days_since_last_push1
active_weeks_last_year32

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 23 days ago
27/27Release cadence — a release every ~22.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv1.22.1
releases_from_tagsno
days_since_latest_release23
mean_days_between_releases22.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?

60Moderate · 17% of overall
How it's scored
23.2/60Stars — 28 stars
6.5/25Forks — 7 forks
8/15Watchers — 28 watchers
Inputs used
forks7
stars28
watchers28
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/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_templateno
How it's scored
59.2/80Monthly downloads — 27,479 downloads/month across packagist
3.2/20Registry dependents — 2 packages depend on it
Inputs used
packagesalleyinteractive/mantle-framework
dependents2
ecosystemspackagist
total_downloads388,449
monthly_downloads27,479
unverified_packages_excluded—

Sustainability & Governance

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

69Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.4/22.5Commit distribution — top contributor authored 89% of commits
13.5/13.5Contributor breadth — 13 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled13
top_contributor_share0.892
How it's scored
31.5/42Issue resolution — 75% of issues closed
26.1/30PR acceptance — 685/786 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-Review — Found 17/19 approved changesets -- score normalized to 8
Inputs used
merged_prs685
open_issues31
closed_issues93
prs_merged_7d1
prs_decided_7d2
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.75
closed_unmerged_prs101
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
14.8/25Owner reach — 114 followers of alleyinteractive
25/25Track record — 273 public repos, account ~14 yr old
Inputs used
followers114
owner_typeOrganization
is_verifiedno
owner_loginalleyinteractive
public_repos273
account_age_days5,233

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 23 days ago
20/20Version history — 123 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesalleyinteractive/mantle-framework
ecosystemspackagist
any_deprecatedno
min_days_since_publish23

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — phpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 15 out of 24 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://mantle.alley.com
10/10Repository description
10/10Topics — 2 topics
0/10Wiki
Inputs used
topicsmantle, wordpress
has_wikino
homepagehttps://mantle.alley.com
docs_sitehttps://mantle.alley.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

73Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.5/2.5CI-Tests — 15 out of 24 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5Code-Review — Found 17/19 approved changesets -- score normalized to 8
2.5/2.5Contributors — project has 6 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 18 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate7.3
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.

69Good · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://mantle.alley.com/llms.txt)
36.7/40Legible commit history — 66 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://mantle.alley.com/llms.txt
legible_history_share0.688
agent_instruction_files.github/copilot-instructions.md, CLAUDE.md
agent_instruction_max_bytes10,978
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — phpcs.xml, phpstan.neon
0/11Static type checking
0/10Reproducible environment
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.04
toolchain_manifests—
dependency_bot_commit_share0.04
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
54.9/55Manageable file sizes — 1/760 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes137,161
source_files_sampled760
oversized_source_files1

Key facts

28GitHub stars
13contributors
148commits, last 12 months
1days since last push
100releases
1bus factor
31open issues
Packagistpackage ecosystems

Data collection warnings

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

More detail

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

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.

1234567712021-042023-072025-10
Major 1Minor 11Patch 56

Each point covers 5 days.

OpenSSF Scorecard 7.3 / 10
7.3aggregate

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-10 10:58 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests15 out of 24 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 17/19 approved changesets -- score normalized to 8
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained18 commit(s) and 1 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 37
RegistryPackageVersion constraintManifest
Packagistalleyinteractive/wp-asset-manager^1.4.0composer.json
Packagistalleyinteractive/wp-caper^2.0.1 || ^3.0.0composer.json
Packagistalleyinteractive/wp-concurrent-remote-requests^1.0.2composer.json
Packagistalleyinteractive/wp-filter-side-effects^1.0 || ^2.0composer.json
Packagistalleyinteractive/wp-type-extensions>=3.0.0 <6.0.0composer.json
Packagistdoctrine/inflector^2.0.8composer.json
Packagistdragonmantank/cron-expression^3.3.3composer.json
Packagistfakerphp/faker^1.24composer.json
Packagistfilp/whoops^2.18.1composer.json
Packagistlaravel/serializable-closure^1.3.1 || ^2.0composer.json
Packagistleague/commonmark^2.9.0composer.json
Packagistleague/flysystem^3.29composer.json
Packagistleague/uri^7.5composer.json
Packagistleague/uri-interfaces^7.5composer.json
Packagistmonolog/monolog^2.9.1composer.json
Packagistmyclabs/deep-copy^1.13composer.json
Packagistnesbot/carbon^3.8.4composer.json
Packagistnette/php-generator^4.1composer.json
Packagistnunomaduro/termwind^1.15.1 || ^2.0composer.json
Packagistpsr/container^1.1.1 || ^2.0.2composer.json
Packagistpsr/log^1.0.1 || ^2.0 || ^3.0composer.json
Packagistpsr/simple-cache^3.0composer.json
Packagistramsey/uuid^4.7.4composer.json
Packagistspatie/backtrace^1.8composer.json
Packagistsymfony/console^7.2composer.json
Packagistsymfony/css-selector^7.2.0composer.json
Packagistsymfony/dom-crawler^7.4.12composer.json
Packagistsymfony/finder^7.2.0composer.json
Packagistsymfony/http-foundation^7.3.7composer.json
Packagistsymfony/http-kernel^7.2.0composer.json
Packagistsymfony/mime^7.2.0composer.json
Packagistsymfony/routing^7.2.0composer.json
Packagistsymfony/string^7.2.0composer.json
Packagistsymfony/var-dumper^7.2.0composer.json
Packagistsymfony/yaml^7.2.0composer.json
Packagistvlucas/phpdotenv^5.6.1composer.json
Packagistvoku/portable-ascii^2.0.1composer.json
All dependencies 74

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

RegistryPackageVersionRelation
Packagistalleyinteractive/wp-asset-manager—direct
Packagistalleyinteractive/wp-caper—direct
Packagistalleyinteractive/wp-concurrent-remote-requests—direct
Packagistalleyinteractive/wp-filter-side-effects—direct
Packagistalleyinteractive/wp-type-extensions—direct
Packagistdoctrine/inflector—direct
Packagistdragonmantank/cron-expression—direct
Packagistfakerphp/faker—direct
Packagistfilp/whoops—direct
Packagistlaravel/serializable-closure—direct
Packagistleague/commonmark—direct
Packagistleague/flysystem—direct
Packagistleague/uri—direct
Packagistleague/uri-interfaces—direct
Packagistmonolog/monolog—direct
Packagistmyclabs/deep-copy—direct
Packagistnesbot/carbon—direct
Packagistnette/php-generator—direct
Packagistnunomaduro/termwind—direct
Packagistpsr/container—direct
Packagistpsr/log—direct
Packagistpsr/simple-cache—direct
Packagistramsey/uuid—direct
Packagistspatie/backtrace—direct
Packagistsymfony/console—direct
Packagistsymfony/css-selector—direct
Packagistsymfony/dom-crawler—direct
Packagistsymfony/finder—direct
Packagistsymfony/http-foundation—direct
Packagistsymfony/http-kernel—direct
Packagistsymfony/mime—direct
Packagistsymfony/routing—direct
Packagistsymfony/string—direct
Packagistsymfony/var-dumper—direct
Packagistsymfony/yaml—direct
Packagistvlucas/phpdotenv—direct
Packagistvoku/portable-ascii—direct
Packagistalleyinteractive/alley-coding-standards—indirect
Packagistalleyinteractive/logger—indirect
Packagistalleyinteractive/wp-match-blocks—indirect
Packagistguzzlehttp/guzzle—indirect
Packagistilluminate/view—indirect
Packagistleague/flysystem-aws-s3-v3—indirect
Packagistmantle-framework/cache—indirect
Packagistmantle-framework/config—indirect
Packagistmantle-framework/console—indirect
Packagistmantle-framework/container—indirect
Packagistmantle-framework/contracts—indirect
Packagistmantle-framework/database—indirect
Packagistmantle-framework/events—indirect
Packagistmantle-framework/facade—indirect
Packagistmantle-framework/faker—indirect
Packagistmantle-framework/filesystem—indirect
Packagistmantle-framework/framework-views—indirect
Packagistmantle-framework/http—indirect
Packagistmantle-framework/http-client—indirect
Packagistmantle-framework/log—indirect
Packagistmantle-framework/support—indirect
Packagistmantle-framework/testing—indirect
Packagistmantle-framework/testing-dependencies—indirect
Packagistmantle-framework/view—indirect
Packagistmockery/mockery—indirect
Packagistnunomaduro/collision—indirect
Packagistphp—indirect
Packagistphp-stubs/wp-cli-stubs—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpunit/phpunit—indirect
Packagistrector/rector—indirect
Packagistspatie/once—indirect
Packagistspatie/phpunit-snapshot-assertions—indirect
Packagistspatie/ray—indirect
Packagistsquizlabs/php_codesniffer—indirect
Packagistsymplify/monorepo-builder—indirect
Packagistszepeviktor/phpstan-wordpress—indirect
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 statistics — Packagist.