Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 15:09 UTC

WyriHaximus / php-phpstan-rules-wrapper

🌯 PHPStan rules wrapper

MIT★ 6 stars⑂ 0 forkssince Mar 2019View on GitHub ↗

WyriHaximus/php-phpstan-rules-wrapper holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (91/100) and lowest on AI Readiness (8/100). It was last updated today. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

Cees-Jan KiewietPersonal account
651 followers537 public repossince Oct 2009@SurveyMonkey

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistwyrihaximus/phpstan-rules-wrapper14.0.0134,2607827 days ago

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 0 days ago
20.8/36Commit cadence30/52 weeks with commits
17.9/18Commit volume97 commits in the last year
10/10OpenSSF Scorecard: Maintained24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year97
human_commit_share
days_since_last_push0
active_weeks_last_year30

Release discipline

100Exceptional
How it's scored
27/27Ships releases78 releases published
36/36Release recencylatest release 27 days ago
27/27Release cadencea release every ~28.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count78
latest_release_tag14.0.0
releases_from_tagsno
days_since_latest_release27
mean_days_between_releases28.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?

39Weak · 17% of overall
How it's scored
11.3/60Stars6 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars6
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/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_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
68.4/80Monthly downloads134,260 downloads/month across packagist
2/20Registry dependents1 packages depend on it
Inputs used
packageswyrihaximus/phpstan-rules-wrapper
dependents1
ecosystemspackagist
total_downloads1,805,828
monthly_downloads134,260
unverified_packages_excluded

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.4/22.5Commit distributiontop contributor authored 54% of commits
8.1/13.5Contributor breadth6 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.536
How it's scored
36.8/42Issue resolution88% of issues closed
25/30PR acceptance192/230 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/1 approved changesets -- score normalized to 0
Inputs used
merged_prs192
open_issues1
closed_issues7
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.875
closed_unmerged_prs38
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
20.2/25Owner reach651 followers of WyriHaximus
25/25Track record537 public repos, account ~16 yr old
Inputs used
followers651
owner_typeUser
is_verified
owner_loginWyriHaximus
public_repos537
account_age_days6,102
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 packagist
35/35Publish recencylatest publish 27 days ago
20/20Version history78 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageswyrihaximus/phpstan-rules-wrapper
ecosystemspackagist
any_deprecatedno
min_days_since_publish27

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsphpstan, php, wrapper, burrito, hacktoberfest
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 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-Tests15 out of 15 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
0/7.5Code-ReviewFound 0/1 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 17 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
7.5/7.5Maintained24 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
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_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.4
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.

8Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Key facts

6GitHub stars
6contributors
97commits, last 12 months
0days since last push
78releases
1bus factor
1open issues
Packagistpackage ecosystems

Data collection warnings

  • Language breakdown unavailable

More detail

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-07-17 15:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/1 approved changesets -- score normalized to 0
10Contributorsproject has 17 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained24 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
Packagistergebnis/phpstan-rules^2.13.1composer.json
Packagistshipmonk/dead-code-detector^1.3.0composer.json
Packagistshipmonk/phpstan-rules^4.4.0composer.json
Packagiststaabm/phpstan-psr3^1.0.3composer.json
Packagistsymplify/phpstan-extensions^12.0.2composer.json
Packagisttomasvotruba/type-coverage^2.2.2composer.json
Packagistwyrihaximus/phpstan-no-safe^1.0.0composer.json
Packagistyamadashy/phpstan-friendly-formatter^1.4.0composer.json
All dependencies 17

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

RegistryPackageVersionRelation
Packagistergebnis/phpstan-rules2.13.1direct
Packagistshipmonk/dead-code-detector1.3.0direct
Packagistshipmonk/phpstan-rules4.4.0direct
Packagiststaabm/phpstan-psr31.0.3direct
Packagistsymplify/phpstan-extensions12.0.2direct
Packagisttomasvotruba/type-coverage2.2.2direct
Packagistwyrihaximus/phpstan-no-safe1.0.0direct
Packagistyamadashy/phpstan-friendly-formatter1.4.0direct
Packagistphp-parallel-lint/php-console-color1.0.1indirect
Packagistphp-parallel-lint/php-console-highlighter1.0.0indirect
Packagistphpstan/extension-installer1.4.3indirect
Packagistphpstan/phpstan2.2.3indirect
Packagistphpstan/phpstan-deprecation-rules2.0.4indirect
Packagistphpstan/phpstan-mockery2.0.0indirect
Packagistphpstan/phpstan-phpunit2.0.16indirect
Packagistphpstan/phpstan-strict-rules2.0.11indirect
Packagistpsr/log3.0.2indirect
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.11.0 — full methodology · metrics wiki.

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