Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-03 06:52 UTC

bernat / best_in_place

A RESTful unobtrusive jQuery Inplace-Editor and a helper as a Rails Gem

Ruby · HTML · JavaScriptNo license detected★ 1,185 stars⑂ 562 forkssince Dec 2010forkView on GitHub ↗
KindLibraryCommand-line toolPluginNetwork servicehow this is determined

bernat/best_in_place holds a health index of 25 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (67/100) and lowest on Vitality (15/100). It was last updated 778 days ago. 3 contributors account for most of its recent work.

25
overall / 100
At Risk

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.

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

Ownership

BernatPersonal account
52 followers16 public repossince Nov 2009Itnig

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
RubyGemsbest_in_place4.0.0-37778 days ago

Metrics by category

Vitality

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

15Critical · 21% of overall
How it's scored
0/36Push recency — last push 778 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push778
active_weeks_last_year0
How it's scored
27/27Ships releases — 2 releases published
0/36Release recency — latest release 778 days ago
5.4/27Release cadence — a release every ~2,645.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv4.0.0
releases_from_tagsno
days_since_latest_release778
mean_days_between_releases2,645.8
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?

56Moderate · 17% of overall
How it's scored
49.9/60Stars — 1,185 stars
22.9/25Forks — 562 forks
8.1/15Watchers — 30 watchers
Inputs used
forks562
stars1,185
watchers30
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicestravis-ci.org
has_pull_request_templateno
How it's scored
72.5/80Total downloads — 9,491,791 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbest_in_place
dependents—
ecosystemsrubygems
total_downloads9,491,791
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?

67Good · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.6/22.5Commit distribution — top contributor authored 31% of commits
13.5/13.5Contributor breadth — 75 contributors
10/10OpenSSF Scorecard: Contributors — project has 20 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled75
top_contributor_share0.307
How it's scored
30.3/42Issue resolution — 72% of issues closed
18.1/30PR acceptance — 142/235 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 13/18 approved changesets -- score normalized to 7
Inputs used
merged_prs142
open_issues107
closed_issues278
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.722
closed_unmerged_prs93
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
12.4/25Owner reach — 52 followers of bernat
21/25Track record — 16 public repos, account ~16 yr old
Inputs used
followers52
owner_typeUser
is_verified—
owner_loginbernat
public_repos16
account_age_days6,165
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
4/35Publish recency — latest publish 778 days ago
20/20Version history — 37 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbest_in_place
ecosystemsrubygems
any_deprecatedno
min_days_since_publish778

Engineering Quality

Are baseline engineering and documentation practices in place?

35Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 14 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

15Critical
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage site — http://blog.bernatfarrero.com/in-place-editing-with-javascript-jquery-and-rails-3/
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttp://blog.bernatfarrero.com/in-place-editing-with-javascript-jquery-and-rails-3/
docs_sitehttp://blog.bernatfarrero.com/in-place-editing-with-javascript-jquery-and-rails-3/
has_readmeno
has_docs_dirno
has_descriptionno

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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 14 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 13/18 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 20 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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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_packages2
unassessed_packages14
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 2 resolved dependencies against OSV. 14 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.

30At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
29.3/40Legible commit history — 55 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.55
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
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
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/40 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes29,374
source_files_sampled40
oversized_source_files0

Key facts

1,185GitHub stars
75contributors
0commits, last 12 months
778days since last push
2releases
3bus factor
107open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 562 ⇿
0Stars
562Forks
2Releases

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.

0100200300400500600562112011-012018-072026-01
Major 1Minor 0Patch 1

Each point covers 14 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-03 06:52 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 14 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 13/18 approved changesets -- score normalized to 7
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
RubyGemsrails-assets-jquery1.11.1Gemfile
RubyGemsrails-assets-jquery-ui1.10.4Gemfile
RubyGemsrdiscount—Gemfile
RubyGemsrspec-rails—Gemfile
RubyGemsnokogiri—Gemfile
RubyGemscombustion—Gemfile
RubyGemssprockets-rails—Gemfile
RubyGemscapybara—Gemfile
RubyGemspoltergeist—Gemfile
RubyGemssqlite3—Gemfile
RubyGemsappraisal—Gemfile
RubyGemslaunchy—Gemfile
RubyGemspuma—Gemfile
RubyGemsphantomjs—Gemfile
RubyGemsbyebug—Gemfile
All dependencies 16

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

RegistryPackageVersionRelation
RubyGemsappraisal—direct
RubyGemsbyebug—direct
RubyGemscapybara—direct
RubyGemscombustion—direct
RubyGemslaunchy—direct
RubyGemsnokogiri—direct
RubyGemspoltergeist—direct
RubyGemsrails-assets-jquery1.11.1direct
RubyGemsrails-assets-jquery-ui1.10.4direct
RubyGemsrdiscount—direct
RubyGemsrspec-rails—direct
RubyGemssprockets-rails—direct
RubyGemssqlite3—direct
RubyGemsactionpack—indirect
RubyGemsactiverecord—indirect
RubyGemsrailties—indirect
Dependency advisories 0

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