Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-12 16:25 UTC

AlchemyCMS / alchemy-solidus

AlchemyCMS Solidus Integration

Ruby · HTMLBSD-3-Clause★ 31 stars⑂ 29 forkssince Dec 2015View on GitHub ↗
KindLibraryNetwork servicehow this is determined

AlchemyCMS/alchemy-solidus holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on AI Readiness (38/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

23 followers34 public repossince Dec 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsalchemy-solidus8.4.0-510 days ago

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
7.6/36Commit cadence — 11/52 weeks with commits
16.3/18Commit volume — 64 commits in the last year
9/10OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year64
human_commit_share1
days_since_last_push0
active_weeks_last_year11
How it's scored
27/27Ships releases — 45 releases published
36/36Release recency — latest release 0 days ago
19.8/27Release cadence — a release every ~78.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count45
latest_release_tagv8.4.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases78.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?

50Moderate · 17% of overall
How it's scored
24/60Stars — 31 stars
12.1/25Forks — 29 forks
3.3/15Watchers — 5 watchers
Inputs used
forks29
stars31
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateno
How it's scored
53/80Total downloads — 125,761 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesalchemy-solidus
dependents—
ecosystemsrubygems
total_downloads125,761
monthly_downloads—
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

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 factor — 1 contributor(s) cover half of all commits
2.6/22.5Commit distribution — top contributor authored 88% of commits
13.5/13.5Contributor breadth — 17 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.884
How it's scored
42/42Issue resolution — 100% of issues closed
26.8/30PR acceptance — 117/131 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 3/8 approved changesets -- score normalized to 3
Inputs used
merged_prs117
open_issues0
closed_issues21
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs14
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.9/25Owner reach — 23 followers of AlchemyCMS
23.2/25Track record — 34 public repos, account ~12 yr old
Inputs used
followers23
owner_typeOrganization
is_verifiedno
owner_loginAlchemyCMS
public_repos34
account_age_days4,680

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 0 days ago
20/20Version history — 51 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesalchemy-solidus
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://alchemy-cms.com
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicssolidus, alchemy, ecommerce, frontend, cms
has_wikiyes
homepagehttps://alchemy-cms.com
docs_sitehttps://alchemy-cms.com
has_readmeyes
has_docs_dirno
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-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 3/8 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 5 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
6.8/7.5Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
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 — 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_aggregate4.8
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
advisories0
affected_packages0
assessed_packages1
unassessed_packages28
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. 28 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.

38Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
33.6/40Legible commit history — 63 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.63
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
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_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/88 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes6,589
source_files_sampled88
oversized_source_files0

Key facts

31GitHub stars
17contributors
64commits, last 12 months
0days since last push
45releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 29 ⇿
0Stars
29Forks
38Releases

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.

0510152025302822015-122020-082025-03
Major 6Minor 16Patch 16

Each point covers 9 days.

OpenSSF Scorecard 4.8 / 10
4.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-10-12 16:25 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 3/8 approved changesets -- score normalized to 3
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 17
RegistryPackageVersion constraintManifest
RubyGemssolidus_core—Gemfile
RubyGemssolidus_backend—Gemfile
RubyGemssolidus_frontend—Gemfile
RubyGemsalchemy_cms—Gemfile
RubyGemsalchemy-devise—Gemfile
RubyGemssqlite3~> 2.7Gemfile
RubyGemspry-rails—Gemfile
RubyGemssprockets~> 4.0Gemfile
RubyGemsjsbundling-rails~> 1.1Gemfile
RubyGemsrails>= 6.1.0Gemfile
RubyGemslisten—Gemfile
RubyGemsdeface—Gemfile
RubyGemsconcurrent-ruby< 1.3.5Gemfile
RubyGemsrubocop—Gemfile
RubyGemsstandard~> 1.25Gemfile
RubyGemsruby-lsp-rspec~> 0.1.28Gemfile
RubyGemsjson< 3Gemfile
All dependencies 29

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

RegistryPackageVersionRelation
RubyGemsalchemy_cms—direct
RubyGemsconcurrent-ruby—direct
RubyGemsdeface—direct
RubyGemsjsbundling-rails—direct
RubyGemsjson—direct
RubyGemslisten—direct
RubyGemspry-rails—direct
RubyGemsrails—direct
RubyGemsrubocop—direct
RubyGemsruby-lsp-rspec—direct
RubyGemssolidus_backend—direct
RubyGemssolidus_core—direct
RubyGemssolidus_frontend—direct
RubyGemssprockets—direct
RubyGemssqlite3—direct
RubyGemsstandard—direct
RubyGemsalchemy-solidus—indirect
RubyGemscapybara—indirect
RubyGemscapybara-screenshot—indirect
RubyGemsexecjs2.7.0indirect
RubyGemsfactory_bot—indirect
RubyGemsffaker—indirect
RubyGemsgithub_changelog_generator—indirect
RubyGemspuma—indirect
RubyGemsrspec-rails—indirect
RubyGemsselenium-webdriver—indirect
RubyGemsshoulda-matchers—indirect
RubyGemssolidus_api—indirect
RubyGemssolidus_support—indirect
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. 28 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.34.0 — full methodology · metrics wiki.

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