Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 08:01 UTC

eliashaeussler / typo3-warming

🚀 Extension for TYPO3 CMS that warms up Frontend caches based on an XML sitemap with multi-language support.

PHP · TypeScriptGPL-2.0★ 22 stars⑂ 11 forkssince Apr 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

eliashaeussler/typo3-warming 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 AI Readiness (50/100). It was last updated today. 2 contributors account 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

Elias HäußlerPersonal account
80 followers105 public repossince Dec 2015

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
Packagisteliashaeussler/typo3-warming5.3.211,40310240 days ago

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
34.6/36Commit cadence50/52 weeks with commits
18/18Commit volume859 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year859
human_commit_share
days_since_last_push0
active_weeks_last_year50
How it's scored
27/27Ships releases84 releases published
36/36Release recencylatest release 40 days ago
27/27Release cadencea release every ~19 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count84
latest_release_tag5.3.2
releases_from_tagsno
days_since_latest_release40
mean_days_between_releases19

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

55Moderate · 17% of overall
How it's scored
21.4/60Stars22 stars
8.3/25Forks11 forks
0/15Watchers1 watchers
Inputs used
forks11
stars22
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
54.1/80Monthly downloads11,403 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packageseliashaeussler/typo3-warming
dependents0
ecosystemspackagist
total_downloads266,358
monthly_downloads11,403
unverified_packages_excluded

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.4/22.5Commit distributiontop contributor authored 45% of commits
12.2/13.5Contributor breadth9 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled9
top_contributor_share0.447
How it's scored
39.4/42Issue resolution94% of issues closed
27.9/30PR acceptance1,056/1,137 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/19 approved changesets -- score normalized to 0
Inputs used
merged_prs1,056
open_issues3
closed_issues46
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.939
closed_unmerged_prs81
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
13.7/25Owner reach80 followers of eliashaeussler
25/25Track record105 public repos, account ~10 yr old
Inputs used
followers80
owner_typeUser
is_verified
owner_logineliashaeussler
public_repos105
account_age_days3,865
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 40 days ago
20/20Version history102 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageseliashaeussler/typo3-warming
ecosystemspackagist
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.php, eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.typo3.org/p/eliashaeussler/typo3-warming/main/en-us/
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicstypo3, extension, cache, cache-warmup, warming, xml-sitemap
has_wikino
homepagehttps://docs.typo3.org/p/eliashaeussler/typo3-warming/main/en-us/
docs_sitehttps://docs.typo3.org/p/eliashaeussler/typo3-warming/main/en-us/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

58Moderate · 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-Tests9 out of 9 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/19 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 4 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.5Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, 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.

50Moderate · 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
11/11Lint / format config.php-cs-fixer.php, eslint.config.js
11/11Static type checkingBuild/assets/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock, package-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsBuild/assets/tsconfig.json
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
27/45Type-checkable codePHP with type-check config (Build/assets/tsconfig.json)
54.7/55Manageable file sizes1/195 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes776,491
source_files_sampled195
oversized_source_files1

Key facts

22GitHub stars
9contributors
859commits, last 12 months
0days since last push
84releases
2bus factor
3open issues
Packagistpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-16 08:01 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests9 out of 9 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/19 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 21
RegistryPackageVersion constraintManifest
Packagistcuyz/valinor^2.0composer.json
Packagisteliashaeussler/cache-warmup^5.0composer.json
Packagisteliashaeussler/sse^2.0composer.json
Packagisteliashaeussler/typo3-sitemap-locator^1.0composer.json
Packagistguzzlehttp/guzzle^7.10composer.json
Packagistguzzlehttp/promises^2.0composer.json
Packagistmteu/typo3-typed-extconf^1.0composer.json
Packagistpsr/event-dispatcher^1.0composer.json
Packagistpsr/http-message^1.1 || ^2.0composer.json
Packagistpsr/http-server-handler^1.0composer.json
Packagistpsr/http-server-middleware^1.0composer.json
Packagistpsr/log^3.0composer.json
Packagistsymfony/console^7.2 || ^8.0composer.json
Packagistsymfony/dependency-injection^7.2 || ^8.0composer.json
Packagistsymfony/expression-language^7.2 || ^8.0composer.json
Packagistsymfony/options-resolver^7.2 || ^8.0composer.json
Packagisttypo3/cms-backend~13.4.5 || ~14.3.0composer.json
Packagisttypo3/cms-core~13.4.5 || ~14.3.0composer.json
Packagisttypo3/cms-extbase~13.4.5 || ~14.3.0composer.json
Packagisttypo3/cms-fluid~13.4.5 || ~14.3.0composer.json
Packagisttypo3/cms-frontend~13.4.5 || ~14.3.0composer.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.