Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 12:25 UTC

KentaaNL / capistrano-asg-rolling

Capistrano plugin for performing rolling updates to AWS Auto Scaling Groups using Instance Refresh.

RubyMIT★ 3 stars⑂ 4 forkssince Oct 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

KentaaNL/capistrano-asg-rolling holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Engineering Quality (78/100) and lowest on AI Readiness (39/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

KentaaOrganization · verified domain
1 follower20 public repossince Oct 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemscapistrano-asg-rolling0.9.0-120 days ago

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9/36Commit cadence13/52 weeks with commits
16.3/18Commit volume65 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_year65
human_commit_share1
days_since_last_push0
active_weeks_last_year13
How it's scored
27/27Ships releases12 releases published
36/36Release recencylatest release 0 days ago
12.6/27Release cadencea release every ~136.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count12
latest_release_tagv0.9.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases136.5
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?

42Weak · 17% of overall
How it's scored
4.9/60Stars3 stars
4/25Forks4 forks
2.7/15Watchers4 watchers
Inputs used
forks4
stars3
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateno
How it's scored
47.1/80Total downloads33,830 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagescapistrano-asg-rolling
dependents
ecosystemsrubygems
total_downloads33,830
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
1.6/22.5Commit distributiontop contributor authored 93% of commits
5.4/13.5Contributor breadth4 contributors
10/10OpenSSF Scorecard: Contributorsproject has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.929
How it's scored
42/42Issue resolution100% of issues closed
27.9/30PR acceptance13/14 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs13
open_issues0
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs1
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
20/20Verified domain
2.2/25Owner reach1 followers of KentaaNL
21.6/25Track record20 public repos, account ~14 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedyes
owner_loginKentaaNL
public_repos20
account_age_days5,419

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 0 days ago
20/20Version history12 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagescapistrano-asg-rolling
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows1 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
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 sitehttps://www.rubydoc.info/gems/capistrano-asg-rolling/0.9.0
10/10Repository description
10/10Topics7 topics
10/10Wiki
Inputs used
topicscapistrano, rolling-update, auto-scaling, auto-scaling-group, aws, deployment, ruby
has_wikiyes
homepage
docs_sitehttps://www.rubydoc.info/gems/capistrano-asg-rolling/0.9.0
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 8 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/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/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. 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
advisories0
affected_packages0
assessed_packages51
unassessed_packages9
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 51 resolved dependencies against OSV. 9 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.

39Weak · 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.aws.amazon.com/llms.txt)
11.2/40Legible commit history21 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.aws.amazon.com/llms.txt
legible_history_share0.21
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
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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 codeRuby without a type-check config
55/55Manageable file sizes0/37 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes33,247
source_files_sampled37
oversized_source_files0

Key facts

3GitHub stars
4contributors
65commits, last 12 months
0days since last push
12releases
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 ★ / 4 ⇿
0Stars
4Forks
4Releases

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.

1223344412023-042023-112024-05
Major 0Minor 2Patch 2

Each point covers 2 days.

OpenSSF Scorecard 4.2 / 10
4.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-08-28 12:25 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 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 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
0SASTno SAST tool detected
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 4
RegistryPackageVersion constraintManifest
RubyGemsrubocop~> 1.58Gemfile
RubyGemsrubocop-performance~> 1.20Gemfile
RubyGemsrubocop-rake~> 0.6Gemfile
RubyGemsrubocop-rspec~> 3.0Gemfile
All dependencies 60

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

RegistryPackageVersionRelation
RubyGemsrubocop1.90.0direct
RubyGemsrubocop-performance1.27.0direct
RubyGemsrubocop-rake0.7.1direct
RubyGemsrubocop-rspec3.10.2direct
RubyGemsaddressable2.9.0indirect
RubyGemsairbrussh1.6.2indirect
RubyGemsast2.4.3indirect
RubyGemsaws-eventstream1.4.0indirect
RubyGemsaws-partitions1.1282.0indirect
RubyGemsaws-sdk-autoscalingindirect
RubyGemsaws-sdk-autoscaling1.166.0indirect
RubyGemsaws-sdk-core3.254.1indirect
RubyGemsaws-sdk-ec2indirect
RubyGemsaws-sdk-ec21.641.0indirect
RubyGemsaws-sigv41.12.1indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbundlerindirect
RubyGemscapistranoindirect
RubyGemscapistrano3.20.1indirect
RubyGemsconcurrent-rubyindirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemscrack1.0.1indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemshashdiff1.2.1indirect
RubyGemsi18n1.15.2indirect
RubyGemsjmespath1.6.2indirect
RubyGemsjson2.21.2indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsnet-scp4.1.0indirect
RubyGemsnet-sftp4.0.0indirect
RubyGemsnet-ssh7.3.3indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel1.28.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemsprism1.9.0indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrakeindirect
RubyGemsrake13.4.2indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrspecindirect
RubyGemsrspec3.13.2indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssimplecovindirect
RubyGemssimplecov1.1.1indirect
RubyGemssshkit1.25.1indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemswebmockindirect
RubyGemswebmock3.26.3indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 51 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 9 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 statisticsRubyGems.