Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 00:12 UTC

Sylius / CmsPlugin

Seamless CMS capabilities for Sylius stores

PHPMIT★ 18 stars⑂ 34 forkssince Apr 2025View on GitHub ↗

Sylius/CmsPlugin holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (84/100) and lowest on AI Readiness (30/100). It was last updated 12 days ago. 4 contributors account for most of its recent work.

78
overall / 100
Good

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.

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

Ownership

Sylius eCommerceOrganization · verified domain
205 followers168 public repossince Apr 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistsylius/cms-pluginv1.1.613,13513260 days agosyliussylius-pluginsylius-cms

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
28.8/36Push recency — last push 12 days ago
14.5/36Commit cadence — 21/52 weeks with commits
17.5/18Commit volume — 88 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year88
human_commit_share0.98
days_since_last_push12
active_weeks_last_year21
How it's scored
27/27Ships releases — 13 releases published
16.2/36Release recency — latest release 260 days ago
27/27Release cadence — a release every ~19.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count13
latest_release_tagv1.1.6
releases_from_tagsno
days_since_latest_release260
mean_days_between_releases19.3
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?

56Moderate · 17% of overall
How it's scored
20/60Stars — 18 stars
12.7/25Forks — 34 forks
5/15Watchers — 9 watchers
Inputs used
forks34
stars18
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
54.9/80Monthly downloads — 13,135 downloads/month across packagist
2/20Registry dependents — 1 packages depend on it
Inputs used
packagessylius/cms-plugin
dependents1
ecosystemspackagist
total_downloads126,104
monthly_downloads13,135
unverified_packages_excluded—

Sustainability & Governance

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

84Excellent · 23% of overall
How it's scored
43.2/54Bus factor — 4 contributor(s) cover half of all commits
17.3/22.5Commit distribution — top contributor authored 23% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 27 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled99
top_contributor_share0.23
How it's scored
32.5/42Issue resolution — 77% of issues closed
22.4/30PR acceptance — 129/173 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs129
open_issues7
closed_issues24
prs_merged_7d0
prs_decided_7d2
prs_merged_30d0
prs_decided_30d2
issue_closed_ratio0.774
closed_unmerged_prs44
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
16.6/25Owner reach — 205 followers of Sylius
25/25Track record — 168 public repos, account ~15 yr old
Inputs used
followers205
owner_typeOrganization
is_verifiedyes
owner_loginSylius
public_repos168
account_age_days5,674
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
26/35Publish recency — latest publish 260 days ago
20/20Version history — 13 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessylius/cms-plugin
ecosystemspackagist
any_deprecatedno
min_days_since_publish260

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 9 out of 11 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
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/10Topics — 3 topics
10/10Wiki
Inputs used
topicscms, sylius, sylius-plugin
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?

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2/2.5CI-Tests — 9 out of 11 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 27 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages1
unassessed_packages42
affected_by_severitymoderate 1
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. 42 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.

30At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
27.2/40Legible commit history — 50 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.51
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/364 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes17,079
source_files_sampled364
oversized_source_files0

Key facts

18GitHub stars
99contributors
88commits, last 12 months
12days since last push
13releases
4bus factor
7open 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 ★ / 34 ⇿
0Stars
34Forks
13Releases

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.

01325383442025-052026-012026-10
Major 1Minor 1Patch 11

Each point covers 2 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-10-22 00:11 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
8CI-Tests9 out of 11 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 27 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Packagistapi-platform/state^4.0.3composer.json
Packagistsylius/sylius^2.0composer.json
Packagistleague/csv^9.1composer.json
Packagistsylius/telemetry^1.0composer.json
Packagistehyiah/ux-quill^3.6composer.json
All dependencies 43

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

RegistryPackageVersionRelation
Packagistapi-platform/state—direct
Packagistehyiah/ux-quill—direct
Packagistleague/csv—direct
Packagistsylius/sylius—direct
Packagistsylius/telemetry—direct
npmquill2.0.3indirect
npmswiper^11.2.6indirect
npmtrix^2.0.0indirect
Packagistbehat/behat—indirect
Packagistdmore/behat-chrome-extension—indirect
Packagistdmore/chrome-mink-driver—indirect
Packagistdoctrine/cache—indirect
Packagistdoctrine/data-fixtures—indirect
Packagistfriends-of-behat/mink—indirect
Packagistfriends-of-behat/mink-browserkit-driver—indirect
Packagistfriends-of-behat/mink-debug-extension—indirect
Packagistfriends-of-behat/mink-extension—indirect
Packagistfriends-of-behat/page-object-extension—indirect
Packagistfriends-of-behat/suite-settings-extension—indirect
Packagistfriends-of-behat/symfony-extension—indirect
Packagistfriends-of-behat/variadic-extension—indirect
Packagistlchrusciel/api-test-case—indirect
Packagistmatthiasnoback/symfony-config-test—indirect
Packagistmockery/mockery—indirect
Packagistphp—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-doctrine—indirect
Packagistphpstan/phpstan-strict-rules—indirect
Packagistphpstan/phpstan-symfony—indirect
Packagistphpstan/phpstan-webmozart-assert—indirect
Packagistphpunit/phpunit—indirect
Packagistpsr/event-dispatcher—indirect
Packagistrobertfausk/behat-panther-extension—indirect
Packagistsylius-labs/coding-standard—indirect
Packagistsylius-labs/suite-tags-extension—indirect
Packagistsylius/test-application—indirect
Packagistsymfony/browser-kit—indirect
Packagistsymfony/debug-bundle—indirect
Packagistsymfony/dotenv—indirect
Packagistsymfony/flex—indirect
Packagistsymfony/runtime—indirect
Packagistsymfony/web-profiler-bundle—indirect
Dependency advisories 1

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: 1 carry known advisories, of which 0 are direct. 42 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
quill2.0.3indirectmoderate1—

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

How one result sits in the wider record: aggregate statistics — Packagist.