Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 14:11 UTC

algolia / algoliasearch-magento-2

Algolia Search integration for Magento 2 - compatible with versions from 2.3.x to 2.4.x

PHPCustom license★ 191 stars⑂ 172 forkssince Mar 2016View on GitHub ↗
KindPluginLibraryhow this is determined

algolia/algoliasearch-magento-2 holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (98/100) and lowest on Security (50/100). It was last updated 5 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

AlgoliaOrganization · verified domain
867 followers548 public repossince Jul 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistalgolia/algoliasearch-magento-23.19.231,12812222 days ago

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 514 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year514
human_commit_share1
days_since_last_push5
active_weeks_last_year47

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 22 days ago
27/27Release cadence — a release every ~22.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag3.19.2
releases_from_tagsno
days_since_latest_release22
mean_days_between_releases22.9
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?

76Good · 17% of overall
How it's scored
37/60Stars — 191 stars
18.6/25Forks — 172 forks
10.2/15Watchers — 70 watchers
Inputs used
forks172
stars191
watchers70
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

94Exceptional
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicescircleci.com, shields.io
has_pull_request_templateyes
How it's scored
59.9/80Monthly downloads — 31,128 downloads/month across packagist
8.4/20Registry dependents — 17 packages depend on it
Inputs used
packagesalgolia/algoliasearch-magento-2
dependents17
ecosystemspackagist
total_downloads2,008,455
monthly_downloads31,128
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
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.3/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 65 contributors
10/10OpenSSF Scorecard: Contributors — project has 22 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled65
top_contributor_share0.32
How it's scored
0/42Issue resolution — no issues or no data
26.4/30PR acceptance — 1,430/1,624 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 7/10 approved changesets -- score normalized to 7
Inputs used
merged_prs1,430
open_issues0
closed_issues0
prs_merged_7d3
prs_decided_7d3
prs_merged_30d20
prs_decided_30d20
issue_closed_ratio—
closed_unmerged_prs194
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
21.1/25Owner reach — 867 followers of algolia
25/25Track record — 548 public repos, account ~14 yr old
Inputs used
followers867
owner_typeOrganization
is_verifiedyes
owner_loginalgolia
public_repos548
account_age_days5,201

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 22 days ago
20/20Version history — 122 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesalgolia/algoliasearch-magento-2
ecosystemspackagist
any_deprecatedno
min_days_since_publish22

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 5 out of 10 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.algolia.com/solutions/magento/
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicsalgolia, magento2, search, php, magento2-extension, magento-algoliasearch, algolia-search
has_wikino
homepagehttps://www.algolia.com/solutions/magento/
docs_sitehttps://www.algolia.com/solutions/magento/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.2/2.5CI-Tests — 5 out of 10 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 7/10 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 22 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
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_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, 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.

56Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.algolia.com/llms.txt)
14.9/40Legible commit history — 28 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.algolia.com/llms.txt
legible_history_share0.28
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes3,932
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.php, phpstan.neon
0/11Static type checking
10/10Reproducible environment — Dockerfile
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_dockerfileyes
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 code — PHP without a type-check config
54.5/55Manageable file sizes — 5/518 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes622,073
source_files_sampled518
oversized_source_files5

Key facts

191GitHub stars
65contributors
514commits, last 12 months
5days since last push
100releases
2bus factor
0open 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 ★ / 172 ⇿
0Stars
172Forks
95Releases

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.

0408012016020017052016-062021-062026-07
Major 2Minor 24Patch 55

Each point covers 10 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-20 14:11 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
5CI-Tests5 out of 10 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 7/10 approved changesets -- score normalized to 7
10Contributorsproject has 22 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 0 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
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 3
RegistryPackageVersion constraintManifest
Packagistmagento/framework~103.0composer.json
Packagistalgolia/algoliasearch-client-php^4.40.0composer.json
Packagistguzzlehttp/guzzle^7.15.2composer.json
All dependencies 10

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

RegistryPackageVersionRelation
Packagistalgolia/algoliasearch-client-php—direct
Packagistguzzlehttp/guzzle—direct
Packagistmagento/framework—direct
Packagistext-dom—indirect
Packagistext-json—indirect
Packagistext-mbstring—indirect
Packagistext-pdo—indirect
Packagistphp—indirect
Packagistphpcompatibility/php-compatibility—indirect
Packagistphpunit/phpunit—indirect
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.34.0 — full methodology · metrics wiki.

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