Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-04 16:41 UTC

0exp / armitage

Armitage - a set of linter settings (gems and packages). My own code style (linter settings for ansible, ruby, yaml, javascript and etc).

RubyMIT★ 5 stars⑂ 0 forkssince Jun 2018View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

0exp/armitage holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (59/100) and lowest on AI Readiness (11/100). It was last updated today. A single contributor accounts for most of its recent work.

41
overall / 100
Weak

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.

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

Ownership

Rustam IbragimovPersonal account
138 followers133 public repossince Oct 2017@umbrellio @cado-labs @smart-rb

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsarmitage-rubocop1.91.0.0-1100 days ago

Metrics by category

Vitality

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

37Weak · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
1.4/36Commit cadence — 2/52 weeks with commits
5.4/18Commit volume — 3 commits in the last year
2/10OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year3
human_commit_share1
days_since_last_push0
active_weeks_last_year2
How it's scored
16.2/27Ships releases — 2 version tags (no GitHub releases)
0/36Release recency — latest release 1,568 days ago
5.4/27Release cadence — a release every ~1,294 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv1.30.1
releases_from_tagsyes
days_since_latest_release1,568
mean_days_between_releases1,294
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
9.8/60Stars — 5 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars5
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
56.7/80Total downloads — 288,140 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesarmitage-rubocop
dependents—
ecosystemsrubygems
total_downloads288,140
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
0.2/22.5Commit distribution — top contributor authored 99% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.99
How it's scored
25.7/42Issue resolution — 61% of issues closed
30/30PR acceptance — 15/15 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs15
open_issues7
closed_issues11
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.611
closed_unmerged_prs0
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.4/25Owner reach — 138 followers of 0exp
25/25Track record — 133 public repos, account ~8 yr old
Inputs used
followers138
owner_typeUser
is_verified—
owner_login0exp
public_repos133
account_age_days3,262
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

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 — 110 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesarmitage-rubocop
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.rubydoc.info/gems/armitage-rubocop/1.91.0.0
10/10Repository description
10/10Topics — 9 topics
10/10Wiki
Inputs used
topicscode-style, ruby-code-style, linter, rubocop, armitage-rubocop, ansible-lint, golangci-lint, eslint, armitage-eslint
has_wikiyes
homepage—
docs_sitehttps://www.rubydoc.info/gems/armitage-rubocop/1.91.0.0
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 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.5/2.5License — license file detected
1.5/7.5Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
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_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages47
unassessed_packages0
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 47 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.

11Critical · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — 0 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/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 — no data
Inputs used
has_nixno
has_testsno
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — Ruby without a type-check config
0/55Manageable file sizes — no source files detected
Inputs used
primary_languageRuby
largest_source_bytes—
source_files_sampled0
oversized_source_files0
Excluded from scoring (no data or not applicable): Manageable file sizes. Remaining weights renormalized.

Key facts

5GitHub stars
3contributors
3commits, last 12 months
0days since last push
2releases
1bus factor
7open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-04 16:41 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 47

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

RegistryPackageVersionRelation
RubyGemsactivesupport8.1.4indirect
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.3indirect
RubyGemsbundler4.0.22indirect
RubyGemscoderay1.1.3indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemsdrb2.2.3indirect
RubyGemsi18n1.15.2indirect
RubyGemsio-console0.9.4indirect
RubyGemsjson3.0.2indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmethod_source1.1.0indirect
RubyGemsminitest6.0.6indirect
RubyGemsparallel2.3.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemsprism1.9.0indirect
RubyGemspry0.16.0indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.7indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake13.4.2indirect
RubyGemsrbs4.2.0indirect
RubyGemsregexp_parser2.13.1indirect
RubyGemsreline0.7.0indirect
RubyGemsrubocop1.91.0indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsrubocop-capybara3.0.0indirect
RubyGemsrubocop-factory_bot2.28.0indirect
RubyGemsrubocop-on-rbs2.2.0indirect
RubyGemsrubocop-performance1.27.0indirect
RubyGemsrubocop-rails2.38.0indirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsrubocop-rspec3.10.2indirect
RubyGemsrubocop-rspec_rails2.32.0indirect
RubyGemsrubocop-thread_safety0.8.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsrubydex0.4.1indirect
RubyGemssecurerandom0.4.1indirect
RubyGemstsort0.2.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.3.0indirect
RubyGemsunicode-emoji4.3.0indirect
RubyGemsuri1.1.1indirect
Dependency advisories 0

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

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.