Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 22:14 UTC

cyberark / conjur-api-ruby

Ruby client for the CyberArk Secrets Manager API

RubyApache-2.0★ 3 stars⑂ 4 forkssince Jan 2013View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

cyberark/conjur-api-ruby holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Engineering Quality (78/100) and lowest on AI Readiness (49/100). It was last updated 51 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

CyberArkOrganization
843 followers194 public repossince Aug 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsconjur-api6.3.1-1615 days ago

Metrics by category

Vitality

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

56Moderate · 21% of overall
How it's scored
18/36Push recencylast push 51 days ago
4.2/36Commit cadence6/52 weeks with commits
12.2/18Commit volume22 commits in the last year
8/10OpenSSF Scorecard: Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year22
human_commit_share1
days_since_last_push51
active_weeks_last_year6
How it's scored
27/27Ships releases22 releases published
36/36Release recencylatest release 51 days ago
12.6/27Release cadencea release every ~184.2 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count22
latest_release_tagv6.3.1
releases_from_tagsno
days_since_latest_release51
mean_days_between_releases184.2

Community & Adoption

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

58Moderate · 17% of overall
How it's scored
4.9/60Stars3 stars
4/25Forks4 forks
7.7/15Watchers25 watchers
Inputs used
forks4
stars3
watchers25
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
60.5/80Total downloads664,812 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesconjur-api
dependents
ecosystemsrubygems
total_downloads664,812
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?

77Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
13.6/22.5Commit distributiontop contributor authored 40% of commits
13.5/13.5Contributor breadth39 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled39
top_contributor_share0.395
How it's scored
42/42Issue resolution100% of issues closed
25.8/30PR acceptance161/187 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_prs161
open_issues0
closed_issues35
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs26
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
21/25Owner reach843 followers of cyberark
25/25Track record194 public repos, account ~9 yr old
Inputs used
followers843
owner_typeOrganization
is_verifiedno
owner_logincyberark
public_repos194
account_age_days3,314

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 5 days ago
20/20Version history161 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesconjur-api
ecosystemsrubygems
any_deprecatedno
min_days_since_publish5

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://rubygems.org/gems/conjur-api
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicsruby, api-client, ruby-gem, conjur, core, conjur-sdk, conjbot-notify, conjur-core
has_wikiyes
homepagehttps://rubygems.org/gems/conjur-api
docs_sitehttps://rubygems.org/gems/conjur-api
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
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 6 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
6/7.5Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
6.8/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_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, Packaging. Remaining weights renormalized.

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.

49Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
26.7/40Legible commit history50 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.5
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 environmentDockerfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
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
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/83 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes19,577
source_files_sampled83
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 examplesexample
Inputs used
example_dirsexample
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
39contributors
22commits, last 12 months
51days since last push
22releases
2bus factor
0open 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

More detail

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

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.

1223344412015-092020-052025-01
Major 1Minor 1Patch 8

Each point covers 9 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-05 22:13 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
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 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 18

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

RegistryPackageVersionRelation
RubyGemsactivesupportindirect
RubyGemsaddressableindirect
RubyGemsci_reporter_rspecindirect
RubyGemscucumberindirect
RubyGemsfakefsindirect
RubyGemsio-grabindirect
RubyGemsjson_specindirect
RubyGemsnokogiriindirect
RubyGemspry-byebugindirect
RubyGemsrakeindirect
RubyGemsrdocindirect
RubyGemsrest-clientindirect
RubyGemsrspecindirect
RubyGemsrspec-expectationsindirect
RubyGemssimplecovindirect
RubyGemssimplecov-coberturaindirect
RubyGemswebrickindirect
RubyGemsyardindirect
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.