Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 17:18 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 73 out of 100, placing it in the Good band. It scores highest on Vitality (84/100) and lowest on Community & Adoption (39/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Claricle by RiboseOrganization
0 followers23 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.10-236 days ago

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
9/36Commit cadence — 13/52 weeks with commits
18/18Commit volume — 123 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year123
human_commit_share0.96
days_since_last_push3
active_weeks_last_year13

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 9 releases published
36/36Release recency — latest release 6 days ago
27/27Release cadence — a release every ~8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count9
latest_release_tagv0.2.10
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases8
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?

39Weak · 17% of overall
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 1 forks
0/15Watchers — 0 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.5License — no license file detected
18/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_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
50.2/80Total downloads — 68,393 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessvg_conform
dependents—
ecosystemsrubygems
total_downloads68,393
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 factor — 1 contributor(s) cover half of all commits
4.3/22.5Commit distribution — top contributor authored 81% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 27 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.807
How it's scored
42/42Issue resolution — 100% of issues closed
25.1/30PR acceptance — 66/79 decided PRs merged
12.3/13Newcomer PR acceptance — 19/20 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/16 approved changesets -- score normalized to 0
Inputs used
merged_prs66
open_issues0
closed_issues73
prs_merged_7d8
prs_decided_7d11
prs_merged_30d34
prs_decided_30d43
issue_closed_ratio1
closed_unmerged_prs13
first_time_authors_30d2
first_time_prs_merged_30d19
first_time_prs_decided_30d20
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of claricle
12.2/25Track record — 23 public repos, account ~1 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginclaricle
public_repos23
account_age_days387

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 6 days ago
20/20Version history — 23 published versions
20/20Not deprecated — active, 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?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 13 out of 13 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
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?

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
2.5/2.5CI-Tests — 13 out of 13 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
0/7.5Code-Review — Found 0/16 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 27 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
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 1 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 — detected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
24.6/35Direct dependencies free of known advisories — 1 affected: nokogiri 1.19.4 (low 3.7)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories3
affected_packages1
assessed_packages50
unassessed_packages8
affected_by_severitylow 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 50 resolved dependencies against OSV. 8 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.

65Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
36.7/40Legible commit history — 66 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.688
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,393
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — lockfile
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
lockfilesGemfile.lock
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 code — HTML without a type-check config
55/55Manageable file sizes — 0/194 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes34,711
source_files_sampled194
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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
5contributors
123commits, last 12 months
3days since last push
9releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-11-18 17:18 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-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/16 approved changesets -- score normalized to 0
10Contributorsproject has 27 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 1 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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
RubyGemscanon~>0.1.10Gemfile
RubyGemsleptris>= 1.9.399.0Gemfile
RubyGemslutaml-model~> 0.8.155Gemfile
RubyGemsmoxml~> 0.6.0Gemfile
RubyGemslens_core~> 0.1Gemfile
RubyGemsnokogiri~> 1.16Gemfile
RubyGemsopenssl~> 3.0Gemfile
RubyGemsrake—Gemfile
RubyGemsrspec—Gemfile
RubyGemsrubocop—Gemfile
RubyGemsrubocop-performance—Gemfile
RubyGemsrubocop-rake—Gemfile
RubyGemsrubocop-rspec—Gemfile
All dependencies 58

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

RegistryPackageVersionRelation
RubyGemscanon0.1.23direct
RubyGemslens_core—direct
RubyGemslens_core0.1.0direct
RubyGemsleptris1.9.399.0direct
RubyGemslutaml-model—direct
RubyGemslutaml-model0.8.155direct
RubyGemsmoxml—direct
RubyGemsmoxml0.6.1direct
RubyGemsnokogiri—direct
RubyGemsnokogiri1.19.4direct
RubyGemsopenssl3.3.3direct
RubyGemsrake13.4.2direct
RubyGemsrspec3.13.2direct
RubyGemsrubocop1.92.1direct
RubyGemsrubocop-performance1.27.0direct
RubyGemsrubocop-rake0.7.1direct
RubyGemsrubocop-rspec3.10.2direct
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.3indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemscsv3.3.7indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsffi1.17.4indirect
RubyGemsjson3.1.0indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemsliquid5.14.0indirect
RubyGemsmemo_wise1.13.0indirect
RubyGemsostruct0.6.3indirect
RubyGemspaint2.3.0indirect
RubyGemsparallel2.3.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemsprism1.9.0indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow—indirect
RubyGemsrainbow3.1.1indirect
RubyGemsregexp_parser2.13.1indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsrubyzip3.7.0indirect
RubyGemsstrscan3.1.8indirect
RubyGemstable_tennis—indirect
RubyGemstable_tennis1.0.0indirect
RubyGemsthor—indirect
RubyGemsthor1.5.0indirect
RubyGemsunicode-display_width3.3.0indirect
RubyGemsunicode-emoji4.3.0indirect
RubyGemsunicode-name1.15.1indirect
RubyGemsunicode-types1.12.0indirect
RubyGemsyeptris—indirect
RubyGemsyeptris0.6.65.0indirect
RubyGemsyeptris0.6.65.0-arm-linux-eabihfindirect
RubyGemsyeptris0.6.65.0-arm-linux-musleabihfindirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 50 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 1 are direct. 8 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
nokogiri1.19.4directlow31.19.5

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.