Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 10:45 UTC

bitExpert / phpstan-magento

Magento specific extension for PHPStan

PHPMIT★ 150 stars⑂ 31 forkssince Mar 2019View on GitHub ↗

bitExpert/phpstan-magento holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Engineering Quality (78/100) and lowest on AI Readiness (35/100). It was last updated 36 days ago. A single contributor accounts for most of its recent work.

75
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.

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

Ownership

bitExpert AGOrganization · verified domain
15 followers62 public repossince Feb 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistbitexpert/phpstan-magento0.44.0100,2614136 days ago

Metrics by category

Vitality

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

60Moderate · 21% of overall
How it's scored
18/36Push recency — last push 36 days ago
3.5/36Commit cadence — 5/52 weeks with commits
12.7/18Commit volume — 25 commits in the last year
10/10OpenSSF Scorecard: Maintained — 11 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year25
human_commit_share0.96
days_since_last_push36
active_weeks_last_year5
How it's scored
27/27Ships releases — 41 releases published
36/36Release recency — latest release 36 days ago
12.6/27Release cadence — a release every ~143.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count41
latest_release_tag0.44.0
releases_from_tagsno
days_since_latest_release36
mean_days_between_releases143.8
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?

66Good · 17% of overall
How it's scored
35.3/60Stars — 150 stars
12.3/25Forks — 31 forks
5/15Watchers — 9 watchers
Inputs used
forks31
stars150
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, shields.io
has_pull_request_templateno
How it's scored
66.7/80Monthly downloads — 100,261 downloads/month across packagist
13.9/20Registry dependents — 119 packages depend on it
Inputs used
packagesbitexpert/phpstan-magento
dependents119
ecosystemspackagist
total_downloads2,878,124
monthly_downloads100,261
unverified_packages_excluded—

Sustainability & Governance

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

71Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.2/22.5Commit distribution — top contributor authored 86% of commits
13.5/13.5Contributor breadth — 17 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.86
How it's scored
37.3/42Issue resolution — 89% of issues closed
24.4/30PR acceptance — 233/286 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 6/16 approved changesets -- score normalized to 3
Inputs used
merged_prs233
open_issues8
closed_issues64
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.889
closed_unmerged_prs53
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 backing — organization-owned
20/20Verified domain
8.7/25Owner reach — 15 followers of bitExpert
25/25Track record — 62 public repos, account ~15 yr old
Inputs used
followers15
owner_typeOrganization
is_verifiedyes
owner_loginbitExpert
public_repos62
account_age_days5,740

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 36 days ago
20/20Version history — 41 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbitexpert/phpstan-magento
ecosystemspackagist
any_deprecatedno
min_days_since_publish36

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — phpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 6 out of 11 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

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsphp, magento2, phpstan, phpstan-extension
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?

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
1.2/2.5CI-Tests — 6 out of 11 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 6/16 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 17 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
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 — 11 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.7/40Legible commit history — 30 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.312
agent_instruction_files—
agent_instruction_max_bytes—
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
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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.04
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/66 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes8,744
source_files_sampled66
oversized_source_files0

Key facts

150GitHub stars
17contributors
25commits, last 12 months
36days since last push
41releases
1bus factor
8open 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 ★ / 31 ⇿
0Stars
31Forks
40Releases

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.

0510152025303022019-032022-122026-08
Major 0Minor 36Patch 4

Each point covers 7 days.

OpenSSF Scorecard 5.2 / 10
5.2aggregate

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-10-21 10:44 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
5CI-Tests6 out of 11 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 6/16 approved changesets -- score normalized to 3
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained11 commit(s) and 3 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistlaminas/laminas-code~3.3.0 || ~3.4.1 || ~3.5.1 || ^4.5 || ^4.10composer.json
Packagistsymfony/finder^3.0 || ^4.0 || ^5.0 || ^6.0 || ^7.0composer.json
All dependencies 18

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

RegistryPackageVersionRelation
Packagistlaminas/laminas-code—direct
Packagistsymfony/finder—direct
Packagistcaptainhook/captainhook—indirect
Packagistcaptainhook/plugin-composer—indirect
Packagistext-dom—indirect
Packagistleague/commonmark—indirect
Packagistmadewithlove/license-checker—indirect
Packagistmagento/framework—indirect
Packagistmikey179/vfsstream—indirect
Packagistnette/neon—indirect
Packagistnikic/php-parser—indirect
Packagistphp—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistphpstan/phpstan-strict-rules—indirect
Packagistphpunit/phpunit—indirect
Packagistsquizlabs/php_codesniffer—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.