Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 12:32 UTC

swissup / module-search-mysql-legacy

PHPNo license detected★ 105 stars⑂ 37 forkssince Nov 2020View on GitHub ↗
KindPluginLibraryhow this is determined

swissup/module-search-mysql-legacy holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (68/100) and lowest on AI Readiness (32/100). It was last updated 12 days ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

swissupOrganization
22 followers97 public repossince Nov 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistswissup/module-search-mysql-legacy1.1.143,2461912 days agosearchmysqllegacy

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 12 days ago
2.8/36Commit cadence — 4/52 weeks with commits
9.7/18Commit volume — 11 commits in the last year
6/10OpenSSF Scorecard: Maintained — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year11
human_commit_share1
days_since_last_push12
active_weeks_last_year4
How it's scored
27/27Ships releases — 1 releases published
36/36Release recency — latest release 12 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tag1.1.14
releases_from_tagsno
days_since_latest_release12
mean_days_between_releases—
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?

41Weak · 17% of overall
How it's scored
32.7/60Stars — 105 stars
13/25Forks — 37 forks
5.6/15Watchers — 11 watchers
Inputs used
forks37
stars105
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
46.8/80Monthly downloads — 3,246 downloads/month across packagist
0/20Registry dependents — 0 packages depend on it
Inputs used
packagesswissup/module-search-mysql-legacy
dependents0
ecosystemspackagist
total_downloads98,637
monthly_downloads3,246
unverified_packages_excluded—

Sustainability & Governance

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

68Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8/22.5Commit distribution — top contributor authored 64% of commits
9.5/13.5Contributor breadth — 7 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.643
How it's scored
42/42Issue resolution — 100% of issues closed
30/30PR acceptance — 10/10 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/26 approved changesets -- score normalized to 0
Inputs used
merged_prs10
open_issues0
closed_issues19
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs0
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
30/30Ownership backing — organization-owned
0/20Verified domain
9.8/25Owner reach — 22 followers of swissup
25/25Track record — 97 public repos, account ~10 yr old
Inputs used
followers22
owner_typeOrganization
is_verifiedno
owner_loginswissup
public_repos97
account_age_days3,988

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 12 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesswissup/module-search-mysql-legacy
ecosystemspackagist
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

37Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 1 out of 4 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsmagento, magento2, magento2-extension, magento2-module, magento2-search
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

32At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0.5/2.5CI-Tests — 1 out of 4 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/26 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
4.5/7.5Maintained — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.2
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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
14/40Legible commit history — 22 of 84 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.262
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
10/10Demonstrated agent practice — 5 of the last 84 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.06
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 code — PHP without a type-check config
55/55Manageable file sizes — 0/104 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes20,233
source_files_sampled104
oversized_source_files0

Key facts

105GitHub stars
7contributors
11commits, last 12 months
12days since last push
1releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 37 ⇿
0Stars
37Forks

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.

01325383632021-022023-102026-05

Each point covers 5 days.

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-21 12:32 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
2CI-Tests1 out of 4 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/26 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
6Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
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
Packagistmagento/framework>=102.0composer.json
Packagistmagento/module-checkout>=100.3composer.json
Packagistmagento/module-catalog>=103.0composer.json
Packagistmagento/module-search>=101.0composer.json
Packagistmagento/module-cms>=103.0composer.json
Packagistmagento/module-store>=101.0composer.json
Packagistmagento/module-eav>=102.0composer.json
Packagistmagento/module-catalog-search>=101.0composer.json
Packagistmagento/module-backend>=101.0composer.json
Packagistmagento/module-catalog-inventory>=100.3composer.json
Packagistmagento/module-customer>=102.0composer.json
Packagistswissup/module-core^1.12.26composer.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.34.0 — full methodology · metrics wiki.

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