Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-20 09:36 UTC

sabbelasichon / typo3-rector

Rector for TYPO3

PHPMIT★ 260 stars⑂ 69 forkssince Oct 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

sabbelasichon/typo3-rector holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Security (57/100). It was last updated today. 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

Sebastian SchreiberPersonal account
101 followers85 public repossince Jun 2015Sebastian Schreiber

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 publishTags
Packagistssch/typo3-rectorv3.14.3121,36522218 days agomigrationautomationdevupgraderefactoringrector

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
27/36Commit cadence39/52 weeks with commits
18/18Commit volume161 commits in the last year
10/10OpenSSF Scorecard: Maintained19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year161
human_commit_share
days_since_last_push0
active_weeks_last_year39

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 18 days ago
27/27Release cadencea release every ~20.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv3.14.3
releases_from_tagsno
days_since_latest_release18
mean_days_between_releases20.7
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?

62Moderate · 17% of overall
How it's scored
39.1/60Stars260 stars
15.3/25Forks69 forks
5.3/15Watchers10 watchers
Inputs used
forks69
stars260
watchers10
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
67.8/80Monthly downloads121,365 downloads/month across packagist
16.1/20Registry dependents260 packages depend on it
Inputs used
packagesssch/typo3-rector
dependents260
ecosystemspackagist
total_downloads3,242,226
monthly_downloads121,365
unverified_packages_excluded

Sustainability & Governance

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

70Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.5/22.5Commit distributiontop contributor authored 58% of commits
13.5/13.5Contributor breadth51 contributors
10/10OpenSSF Scorecard: Contributorsproject has 29 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled51
top_contributor_share0.578
How it's scored
41.7/42Issue resolution99% of issues closed
28.2/30PR acceptance1,329/1,412 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 10/23 approved changesets -- score normalized to 4
Inputs used
merged_prs1,329
open_issues27
closed_issues3,414
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.992
closed_unmerged_prs83
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
14.4/25Owner reach101 followers of sabbelasichon
25/25Track record85 public repos, account ~11 yr old
Inputs used
followers101
owner_typeUser
is_verified
owner_loginsabbelasichon
public_repos85
account_age_days4,042
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 18 days ago
20/20Version history222 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesssch/typo3-rector
ecosystemspackagist
any_deprecatedno
min_days_since_publish18

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests17 out of 20 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
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/10Topics8 topics
10/10Wiki
Inputs used
topicsrector, typo3, upgrade, php, instant-upgrades, ast, refactoring, hacktoberfest
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?

57Moderate · 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/2.5CI-Tests17 out of 20 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 10/23 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 29 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.5Maintained19 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_aggregate5.7
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.

59Moderate · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md
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.github/copilot-instructions.md
agent_instruction_max_bytes3,092
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
11/11Lint / format configphpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
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_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/1,490 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes36,293
source_files_sampled1,490
oversized_source_files0

Key facts

260GitHub stars
51contributors
161commits, last 12 months
0days since last push
100releases
1bus factor
27open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-20 09:36 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests17 out of 20 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 10/23 approved changesets -- score normalized to 4
10Contributorsproject has 29 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained19 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
Direct dependencies 12
RegistryPackageVersion constraintManifest
Packagistleague/flysystem^2.0 || ^3.0composer.json
Packagistleague/flysystem-memory^2.0 || ^3.0composer.json
Packagistnette/utils^3.2.10 || ^4.0.4composer.json
Packagistnikic/php-parser^5.7.0composer.json
Packagistrector/rector^2.5.2composer.json
Packagistsymfony/console^5.4 || ^6.4 || ^7.0composer.json
Packagistsymfony/filesystem^5.4 || ^6.4 || ^7.0composer.json
Packagistsymfony/finder^5.4 || ^6.4 || ^7.0composer.json
Packagistsymfony/polyfill-php80^1.28.0composer.json
Packagistsymfony/polyfill-php81^1.28.0composer.json
Packagistsymfony/string^5.4 || ^6.4 || ^7.0composer.json
Packagistwebmozart/assert^1.11.0composer.json
All dependencies 26

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

RegistryPackageVersionRelation
Packagistleague/flysystemdirect
Packagistleague/flysystem-memorydirect
Packagistnette/utilsdirect
Packagistnikic/php-parserdirect
Packagistrector/rectordirect
Packagistsymfony/consoledirect
Packagistsymfony/filesystemdirect
Packagistsymfony/finderdirect
Packagistsymfony/polyfill-php80direct
Packagistsymfony/polyfill-php81direct
Packagistsymfony/stringdirect
Packagistwebmozart/assertdirect
Packagistergebnis/composer-normalizeindirect
Packagistext-jsonindirect
Packagistphpindirect
Packagistphp-parallel-lint/php-parallel-lintindirect
Packagistphpstan/extension-installerindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-deprecation-rulesindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpunit/phpunitindirect
Packagistsymfony/configindirect
Packagistsymfony/dependency-injectionindirect
Packagistsymfony/http-kernelindirect
Packagistsymplify/easy-coding-standardindirect
Packagisttypo3/cms-coreindirect
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.15.0 — full methodology · metrics wiki.

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