Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 14:00 UTC

claricle / svg_conform

SVG conformance validation and remediation

HTML · RubyNo license detected★ 3 stars⑂ 1 forksince Aug 2025View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

claricle/svg_conform holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (78/100) and lowest on Security (1/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

Claricle by RiboseOrganization
0 followers18 public repossince Oct 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemssvg_conform0.2.2-166 days ago

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recencylast push 6 days ago
6.9/36Commit cadence10/52 weeks with commits
17.6/18Commit volume91 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year91
human_commit_share1
days_since_last_push6
active_weeks_last_year10
How it's scored
27/27Ships releases1 releases published
36/36Release recencylatest release 6 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tagv0.2.2
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases

Community & Adoption

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

31At Risk · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
47.3/80Total downloads35,938 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessvg_conform
dependents
ecosystemsrubygems
total_downloads35,938
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2/22.5Commit distributiontop contributor authored 91% of commits
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.91
How it's scored
41.3/42Issue resolution98% of issues closed
25.9/30PR acceptance25/29 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs25
open_issues1
closed_issues61
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.984
closed_unmerged_prs4
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
0/25Owner reach0 followers of claricle
11.1/25Track record18 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginclaricle
public_repos18
account_age_days323

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 6 days ago
20/20Version history16 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessvg_conform
ecosystemsrubygems
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
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?

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifestsGemfile
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

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.

64Moderate · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history71 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.763
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,394
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 93
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
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 codeHTML without a type-check config
55/55Manageable file sizes0/165 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes34,719
source_files_sampled165
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

3GitHub stars
3contributors
91commits, last 12 months
6days since last push
1releases
1bus factor
1open issues
RubyGemspackage 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
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/claricle/svg_conform: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-15T14:00:40Z. Please include `A3D0:437D3:A626C51:A1FDD2B:6AA94F85` when reporting this issue.); skipping Scorecard checks

More detail

Direct dependencies 10
RegistryPackageVersion constraintManifest
RubyGemscanon~>0.1.10Gemfile
RubyGemslutaml-modelGemfile
RubyGemsmoxmlGemfile
RubyGemsopenssl~> 3.0Gemfile
RubyGemsrakeGemfile
RubyGemsrspecGemfile
RubyGemsrubocopGemfile
RubyGemsrubocop-performanceGemfile
RubyGemsrubocop-rakeGemfile
RubyGemsrubocop-rspecGemfile
All dependencies 13

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

RegistryPackageVersionRelation
RubyGemscanondirect
RubyGemslutaml-modeldirect
RubyGemsmoxmldirect
RubyGemsopenssldirect
RubyGemsrakedirect
RubyGemsrspecdirect
RubyGemsrubocopdirect
RubyGemsrubocop-performancedirect
RubyGemsrubocop-rakedirect
RubyGemsrubocop-rspecdirect
RubyGemsrainbowindirect
RubyGemstable_tennisindirect
RubyGemsthorindirect
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 statisticsRubyGems.