Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-23 10:25 UTC

FluidTYPO3 / vhs

TYPO3 extension VHS: Fluid ViewHelpers

PHPCustom license★ 195 stars⑂ 232 forkssince Nov 2012View on GitHub ↗

FluidTYPO3/vhs holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (89/100) and lowest on AI Readiness (26/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

4 followers16 public repossince Mar 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistfluidtypo3/vhs7.2.156,56155119 days agotemplatingutilitytypo3-cmsviewhelperfedextfluid

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
5.5/36Commit cadence8/52 weeks with commits
17.9/18Commit volume97 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year97
human_commit_share1
days_since_last_push0
active_weeks_last_year8
How it's scored
16.2/27Ships releases74 version tags (no GitHub releases)
27/36Release recencylatest release 119 days ago
19.8/27Release cadencea release every ~66.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count74
latest_release_tag7.2.1
releases_from_tagsyes
days_since_latest_release119
mean_days_between_releases66.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?

67Good · 17% of overall
How it's scored
37.1/60Stars195 stars
19.7/25Forks232 forks
7.2/15Watchers21 watchers
Inputs used
forks232
stars195
watchers21
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
63.4/80Monthly downloads56,561 downloads/month across packagist
11.4/20Registry dependents51 packages depend on it
Inputs used
packagesfluidtypo3/vhs
dependents51
ecosystemspackagist
total_downloads4,281,169
monthly_downloads56,561
unverified_packages_excluded

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.3/22.5Commit distributiontop contributor authored 72% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 29 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.722
How it's scored
39.6/42Issue resolution94% of issues closed
23.1/30PR acceptance837/1,087 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs837
open_issues51
closed_issues835
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.942
closed_unmerged_prs250
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
5/25Owner reach4 followers of FluidTYPO3
21/25Track record16 public repos, account ~13 yr old
Inputs used
followers4
owner_typeOrganization
is_verified
owner_loginFluidTYPO3
public_repos16
account_age_days4,873
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 119 days ago
20/20Version history55 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesfluidtypo3/vhs
ecosystemspackagist
any_deprecatedno
min_days_since_publish119

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 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
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://fluidtypo3.org
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicstyposcript, php, typo3-cms, typo3-cms-extension, fluid
has_wikino
homepagehttps://fluidtypo3.org
docs_sitehttps://fluidtypo3.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 29 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages10
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 1 resolved dependencies against OSV. 10 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.6/40Legible commit history3 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.03
agent_instruction_files
agent_instruction_max_bytes
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 agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/364 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes25,717
source_files_sampled364
oversized_source_files0

Key facts

195GitHub stars
100contributors
97commits, last 12 months
0days since last push
74releases
1bus factor
51open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 232 ⇿
0Stars
232Forks
72Releases

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.

0408012016020024022752012-112019-092026-07
Major 6Minor 23Patch 43

Each point covers 13 days.

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-23 10:25 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 29 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 7 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
0SASTno SAST tool detected
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 5
RegistryPackageVersion constraintManifest
Packagisttypo3/cms-core^12 || ^13 || ^14.3 || dev-maincomposer.json
Packagisttypo3/cms-extbase^12 || ^13 || ^14.3 || dev-maincomposer.json
Packagisttypo3/cms-fluid^12 || ^13 || ^14.3 || dev-maincomposer.json
Packagisttypo3/cms-frontend^12 || ^13 || ^14.3 || dev-maincomposer.json
Packagisttypo3/cms-backend^12 || ^13 || ^14.3 || dev-maincomposer.json
All dependencies 11

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

RegistryPackageVersionRelation
Packagisttypo3/cms-backenddirect
Packagisttypo3/cms-coredirect
Packagisttypo3/cms-extbasedirect
Packagisttypo3/cms-fluiddirect
Packagisttypo3/cms-frontenddirect
Packagistext-mbstringindirect
Packagistmikey179/vfsstreamindirect
Packagistphpindirect
Packagistphpstan/phpstan1.12.1indirect
Packagistphpunit/phpunitindirect
Packagistsquizlabs/php_codesnifferindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 10 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.27.0 — full methodology · metrics wiki.

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