Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-02 13:36 UTC

VirtoCommerce / vc-module-x-catalog

The X-Catalog module provides high-performance search queries for catalogue data directly from the search index engine.

C#Custom license★ 0 stars⑂ 4 forkssince Jun 2024View on GitHub ↗
KindNetwork serviceLibraryhow this is determined

VirtoCommerce/vc-module-x-catalog holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (89/100) and lowest on Community & Adoption (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

Virto CommerceOrganization
180 followers237 public repossince Oct 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
NuGetVirtoCommerce.XCatalog.Core3.1019.0-1080 days ago
NuGetVirtoCommerce.XCatalog.Data3.1019.0-1080 days ago

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
25.6/36Commit cadence37/52 weeks with commits
17.7/18Commit volume92 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year92
human_commit_share1
days_since_last_push0
active_weeks_last_year37
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~6 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tag3.1019.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases6

Community & Adoption

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

38Weak · 17% of overall
How it's scored
0/60Stars0 stars
4/25Forks4 forks
4.7/15Watchers8 watchers
Inputs used
forks4
stars0
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, sonarcloud.io
has_pull_request_templateyes
How it's scored
53.2/80Total downloads131,018 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesVirtoCommerce.XCatalog.Core, VirtoCommerce.XCatalog.Data
dependents
ecosystemsnuget
total_downloads131,018
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?

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.1/22.5Commit distributiontop contributor authored 55% of commits
13.5/13.5Contributor breadth16 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled16
top_contributor_share0.55
How it's scored
28/42Issue resolution67% of issues closed
26.8/30PR acceptance92/103 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs92
open_issues1
closed_issues2
prs_merged_7d1
prs_decided_7d1
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio0.667
closed_unmerged_prs11
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 backingorganization-owned
0/20Verified domain
16.2/25Owner reach180 followers of VirtoCommerce
25/25Track record237 public repos, account ~12 yr old
Inputs used
followers180
owner_typeOrganization
is_verifiedno
owner_loginVirtoCommerce
public_repos237
account_age_days4,696

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on nuget
35/35Publish recencylatest publish 0 days ago
20/20Version history108 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesVirtoCommerce.XCatalog.Core, VirtoCommerce.XCatalog.Data
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 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-Tests12 out of 12 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
1.5/7.5Code-ReviewFound 8/30 approved changesets -- score normalized to 2
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages18
unassessed_packages0
affected_by_severityhigh 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 18 resolved dependencies against OSV. 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.virtocommerce.org/llms.txt)
29.3/40Legible commit history55 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.virtocommerce.org/llms.txt
legible_history_share0.55
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapbenchmarks/VirtoCommerce.XCatalog.Benchmark/VirtoCommerce.XCatalog.Benchmark.csproj, src/VirtoCommerce.XCatalog.Core/VirtoCommerce.XCatalog.Core.csproj, src/VirtoCommerce.XCatalog.Data/VirtoCommerce.XCatalog.Data.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.02
toolchain_manifestsbenchmarks/VirtoCommerce.XCatalog.Benchmark/VirtoCommerce.XCatalog.Benchmark.csproj, src/VirtoCommerce.XCatalog.Core/VirtoCommerce.XCatalog.Core.csproj, src/VirtoCommerce.XCatalog.Data/VirtoCommerce.XCatalog.Data.csproj, src/VirtoCommerce.XCatalog.Web/VirtoCommerce.XCatalog.Web.csproj, tests/VirtoCommerce.XCatalog.Tests/VirtoCommerce.XCatalog.Tests.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/176 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes31,033
source_files_sampled176
oversized_source_files0

Key facts

0GitHub stars
16contributors
92commits, last 12 months
0days since last push
100releases
1bus factor
1open issues
package ecosystems

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
60Releases

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.

1223344412024-102025-062026-03
Major 0Minor 55Patch 5

Each point covers 2 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-09-02 13:35 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-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
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
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
NuGetVirtoCommerce.CatalogModule.Core3.1032.0src/VirtoCommerce.XCatalog.Core/VirtoCommerce.XCatalog.Core.csproj
NuGetVirtoCommerce.InventoryModule.Core3.1003.0src/VirtoCommerce.XCatalog.Core/VirtoCommerce.XCatalog.Core.csproj
NuGetVirtoCommerce.MarketingModule.Core3.1005.0src/VirtoCommerce.XCatalog.Core/VirtoCommerce.XCatalog.Core.csproj
NuGetVirtoCommerce.Platform.Core3.1057.0src/VirtoCommerce.XCatalog.Core/VirtoCommerce.XCatalog.Core.csproj
NuGetVirtoCommerce.PricingModule.Core3.1003.0src/VirtoCommerce.XCatalog.Core/VirtoCommerce.XCatalog.Core.csproj
NuGetVirtoCommerce.Xapi.Core3.1020.0src/VirtoCommerce.XCatalog.Core/VirtoCommerce.XCatalog.Core.csproj
NuGetVirtoCommerce.Tools3.1007.0src/VirtoCommerce.XCatalog.Web/VirtoCommerce.XCatalog.Web.csproj
All dependencies 18

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

RegistryPackageVersionRelation
NuGetVirtoCommerce.CatalogModule.Core3.1032.0direct
NuGetVirtoCommerce.InventoryModule.Core3.1003.0direct
NuGetVirtoCommerce.MarketingModule.Core3.1005.0direct
NuGetVirtoCommerce.Platform.Core3.1057.0direct
NuGetVirtoCommerce.PricingModule.Core3.1003.0direct
NuGetVirtoCommerce.Tools3.1007.0direct
NuGetVirtoCommerce.Xapi.Core3.1020.0direct
NuGetAutoFixture4.18.1indirect
NuGetAutoMapper12.0.1indirect
NuGetBenchmarkDotNet0.15.8indirect
NuGetcoverlet.collector10.0.1indirect
NuGetFluentAssertions7.2.0indirect
NuGetMicrosoft.NET.Test.Sdk18.0.1indirect
NuGetMoq4.20.72indirect
NuGetVirtoCommerce.Platform.Caching3.1057.0indirect
NuGetVirtoCommerce.Platform.Modules3.1039.0indirect
NuGetxunit.runner.visualstudio3.1.5indirect
NuGetxunit.v33.2.2indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 18 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
AutoMapper12.0.1indirecthigh116.1.1

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