Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 21:12 UTC

VincentLanglet / Twig-CS-Fixer

A tool to automatically fix Twig Coding Standards issues

PHPMIT★ 346 stars⑂ 39 forkssince Jul 2021View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

VincentLanglet/Twig-CS-Fixer holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on AI Readiness (51/100). It was last updated 45 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Vincent LangletPersonal account
111 followers76 public repossince Oct 2014

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
Packagistvincentlanglet/twig-cs-fixer4.0.2612,6777545 days ago

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
18/36Push recencylast push 45 days ago
12.5/36Commit cadence18/52 weeks with commits
14.2/18Commit volume37 commits in the last year
8/10OpenSSF Scorecard: Maintained6 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year37
human_commit_share1
days_since_last_push45
active_weeks_last_year18

Release discipline

98Exceptional
How it's scored
27/27Ships releases75 releases published
36/36Release recencylatest release 45 days ago
27/27Release cadencea release every ~41.8 days
8/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count75
latest_release_tag4.0.2
releases_from_tagsno
days_since_latest_release45
mean_days_between_releases41.8

Community & Adoption

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

70Good · 17% of overall
How it's scored
41.2/60Stars346 stars
13.2/25Forks39 forks
3.9/15Watchers6 watchers
Inputs used
forks39
stars346
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, poser.pugx.org, shields.io
has_pull_request_templateno
How it's scored
77.2/80Monthly downloads612,677 downloads/month across packagist
13.6/20Registry dependents107 packages depend on it
Inputs used
packagesvincentlanglet/twig-cs-fixer
dependents107
ecosystemspackagist
total_downloads11,102,692
monthly_downloads612,677
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
2.5/22.5Commit distributiontop contributor authored 89% of commits
13.5/13.5Contributor breadth26 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled26
top_contributor_share0.891
How it's scored
41/42Issue resolution98% of issues closed
28/30PR acceptance300/322 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 5/30 approved changesets -- score normalized to 1
Inputs used
merged_prs300
open_issues3
closed_issues124
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.976
closed_unmerged_prs22
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
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.7/25Owner reach111 followers of VincentLanglet
25/25Track record76 public repos, account ~11 yr old
Inputs used
followers111
owner_typeUser
is_verified
owner_loginVincentLanglet
public_repos76
account_age_days4,328
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 45 days ago
20/20Version history75 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesvincentlanglet/twig-cs-fixer
ecosystemspackagist
any_deprecatedno
min_days_since_publish45

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.php, phpstan.neon
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_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://twigcsfixer.github.io/
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicstwig, code-style, coding-standards
has_wikino
homepagehttps://twigcsfixer.github.io/
docs_sitehttps://twigcsfixer.github.io/
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
0/7.5Branch-Protectionno data
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
0.8/7.5Code-ReviewFound 5/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 7 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
6/7.5Maintained6 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 8
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
6/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
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.8
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.99
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.php-cs-fixer.php, phpstan.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-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/184 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes39,093
source_files_sampled184
oversized_source_files0

Key facts

346GitHub stars
26contributors
37commits, last 12 months
45days since last push
75releases
1bus factor
3open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 39 ⇿
0Stars
39Forks
71Releases

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.

0102030403922021-082024-012026-06
Major 4Minor 36Patch 26

Each point covers 5 days.

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-08-13 21:12 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
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
1Code-ReviewFound 5/30 approved changesets -- score normalized to 1
10Contributorsproject has 7 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained6 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 8
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Packagistsymfony/console^5.4.9 || ^6.4 || ^7.0 || ^8.0composer.json
Packagistsymfony/filesystem^5.4 || ^6.4 || ^7.0 || ^8.0composer.json
Packagistsymfony/finder^5.4 || ^6.4 || ^7.0 || ^8.0composer.json
Packagistsymfony/string^5.4.42 || ^6.4.10 || ~7.0.10 || ^7.1.3 || ^8.0composer.json
Packagisttwig/twig^3.15composer.json
Packagistwebmozart/assert^1.10 || ^2.0composer.json
All dependencies 27

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

RegistryPackageVersionRelation
Packagistsymfony/consoledirect
Packagistsymfony/filesystemdirect
Packagistsymfony/finderdirect
Packagistsymfony/stringdirect
Packagisttwig/twigdirect
Packagistwebmozart/assertdirect
Packagistcomposer-runtime-apiindirect
Packagistcomposer/semverindirect
Packagistdereuromark/composer-prefer-lowestindirect
Packagistergebnis/composer-normalizeindirect
Packagistext-ctypeindirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistinfection/infectionindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-deprecation-rulesindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpstan/phpstan-strict-rulesindirect
Packagistphpstan/phpstan-symfonyindirect
Packagistphpstan/phpstan-webmozart-assertindirect
Packagistphpunit/phpunitindirect
Packagistrector/rectorindirect
Packagistshipmonk/composer-dependency-analyserindirect
Packagistsymfony/processindirect
Packagistsymfony/twig-bridgeindirect
Packagistsymfony/ux-twig-componentindirect
Packagisttwig/cache-extraindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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

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