Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 16:20 UTC

shipmonk-rnd / phpstan-rules

📏 Various extra strict PHPStan rules we found useful in ShipMonk.

PHPMIT★ 155 stars⑂ 23 forkssince Jun 2022View on GitHub ↗

shipmonk-rnd/phpstan-rules holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (85/100) and lowest on AI Readiness (31/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

ShipMonk R&DOrganization
80 followers27 public repossince Aug 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistshipmonk/phpstan-rules4.4.0228,9195560 days agostatic-analysisphpstan

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
14.5/36Commit cadence21/52 weeks with commits
14.3/18Commit volume38 commits in the last year
10/10OpenSSF Scorecard: Maintained10 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year38
human_commit_share
days_since_last_push0
active_weeks_last_year21

Release discipline

100Exceptional
How it's scored
27/27Ships releases55 releases published
36/36Release recencylatest release 59 days ago
27/27Release cadencea release every ~28.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count55
latest_release_tag4.4.0
releases_from_tagsno
days_since_latest_release59
mean_days_between_releases28.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?

59Moderate · 17% of overall
How it's scored
35.5/60Stars155 stars
11.2/25Forks23 forks
2.7/15Watchers4 watchers
Inputs used
forks23
stars155
watchers4
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
71.5/80Monthly downloads228,919 downloads/month across packagist
14.1/20Registry dependents129 packages depend on it
Inputs used
packagesshipmonk/phpstan-rules
dependents129
ecosystemspackagist
total_downloads2,336,429
monthly_downloads228,919
unverified_packages_excluded

Sustainability & Governance

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

73Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.5/22.5Commit distributiontop contributor authored 71% of commits
13.5/13.5Contributor breadth21 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled21
top_contributor_share0.71
How it's scored
40.7/42Issue resolution97% of issues closed
27.2/30PR acceptance300/331 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 14/30 approved changesets -- score normalized to 4
Inputs used
merged_prs300
open_issues1
closed_issues31
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.969
closed_unmerged_prs31
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
13.7/25Owner reach80 followers of shipmonk-rnd
20.4/25Track record27 public repos, account ~4 yr old
Inputs used
followers80
owner_typeOrganization
is_verified
owner_loginshipmonk-rnd
public_repos27
account_age_days1,794
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 60 days ago
20/20Version history55 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesshipmonk/phpstan-rules
ecosystemspackagist
any_deprecatedno
min_days_since_publish60

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics7 topics
10/10Wiki
Inputs used
topicsphp, phpstan, phpstan-rules, phpstan-strict, checker, ci, extension
has_wikiyes
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?

61Moderate · 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
2.5/2.5CI-Tests30 out of 30 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
3/7.5Code-ReviewFound 14/30 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 6 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.5Maintained10 commit(s) and 2 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_aggregate6.1
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.

31At Risk · 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
22/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_testsyes
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.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/143 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes21,066
source_files_sampled143
oversized_source_files0

Key facts

155GitHub stars
21contributors
38commits, last 12 months
0days since last push
55releases
1bus factor
1open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 6.1 / 10
6.1aggregate

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 16:20 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 14/30 approved changesets -- score normalized to 4
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained10 commit(s) and 2 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
All dependencies 52

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

RegistryPackageVersionRelation
Packagistdealerdirect/phpcodesniffer-composer-installer1.2.1indirect
Packagisteditorconfig-checker/editorconfig-checker10.7.0indirect
Packagistergebnis/composer-normalize2.52.0indirect
Packagistergebnis/json1.6.0indirect
Packagistergebnis/json-normalizer4.10.1indirect
Packagistergebnis/json-pointer3.8.0indirect
Packagistergebnis/json-printer3.8.1indirect
Packagistergebnis/json-schema-validator4.5.1indirect
Packagistjustinrainbow/json-schema6.8.2indirect
Packagistlocalheinz/diff1.3.0indirect
Packagistmarc-mabe/php-enum4.7.2indirect
Packagistmyclabs/deep-copy1.13.4indirect
Packagistnette/schema1.3.5indirect
Packagistnette/utils4.1.4indirect
Packagistnikic/php-parser5.7.0indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphpstan/phpdoc-parser2.3.2indirect
Packagistphpstan/phpstan2.1.54indirect
Packagistphpstan/phpstan-deprecation-rules2.0.4indirect
Packagistphpstan/phpstan-phpunit2.0.16indirect
Packagistphpstan/phpstan-strict-rules2.0.11indirect
Packagistphpunit/php-code-coverage10.1.16indirect
Packagistphpunit/php-file-iterator4.1.0indirect
Packagistphpunit/php-invoker4.0.0indirect
Packagistphpunit/php-text-template3.0.1indirect
Packagistphpunit/php-timer6.0.0indirect
Packagistphpunit/phpunit10.5.63indirect
Packagistsebastian/cli-parser2.0.1indirect
Packagistsebastian/code-unit2.0.0indirect
Packagistsebastian/code-unit-reverse-lookup3.0.0indirect
Packagistsebastian/comparator5.0.5indirect
Packagistsebastian/complexity3.2.0indirect
Packagistsebastian/diff5.1.1indirect
Packagistsebastian/environment6.1.0indirect
Packagistsebastian/exporter5.1.4indirect
Packagistsebastian/global-state6.0.2indirect
Packagistsebastian/lines-of-code2.0.2indirect
Packagistsebastian/object-enumerator5.0.0indirect
Packagistsebastian/object-reflector3.0.0indirect
Packagistsebastian/recursion-context5.0.1indirect
Packagistsebastian/type4.0.0indirect
Packagistsebastian/version4.0.1indirect
Packagistshipmonk/coding-standard0.3.0indirect
Packagistshipmonk/composer-dependency-analyser1.8.4indirect
Packagistshipmonk/coverage-guard1.1.0indirect
Packagistshipmonk/dead-code-detector1.1.2indirect
Packagistshipmonk/name-collision-detector2.1.1indirect
Packagistshipmonk/phpstan-dev0.1.6indirect
Packagistslevomat/coding-standard8.29.0indirect
Packagistsquizlabs/php_codesniffer4.0.1indirect
Packagisttheseer/tokenizer1.3.1indirect
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.12.0 — full methodology · metrics wiki.

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