Claude Code Rails Upgrade Skill

🤖 The one and only Claude Code Skill to Upgrade Rails by FastRuby.io -- Based on 60,000 dev/hours of experience upgrading Rails from 2.3 all the way to 8.1. Dual boot your Rails application and gradually upgrade one minor version at a time. 🚀

Agent Skills Ruby Listed MIT

Is Claude Code Rails Upgrade Skill safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.1 / 10
Provenance None
Signed commits 12%
Last push 3d ago
Compare Claude Code Rails Upgrade Skill
Suggest a correction

In detail: Claude Code Rails Upgrade Skill scores 56.3/100 (Grade C), ranked #149 of 371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 12% of recent commits are signed; last pushed 2026-10-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Code Rails Upgrade Skill could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Claude Code Rails Upgrade Skill and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/ombulabs/claude-code_rails-upgrade-skill, MIT, last pushed 2026-10-12. 12% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 10
  3. Published packages None

    No registry package. Claude Code Rails Upgrade Skill is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 5.8/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Claude Code Rails Upgrade Skill’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Claude Code Rails Upgrade Skill compares in Agent Skills

  1. #147 Claude Code My Workflow 56.4 +0.1
  2. #148 Rampstackco Claude Skills 56.3 ±0
  3. #149 Claude Code Rails Upgrade Skill 56.3 this agent
  4. #150 Aaron Marketing Skills 56.3 ±0
  5. #151 Understand Anything 56.2 −0.1

Bars show each HVTrust score; the tick marks Claude Code Rails Upgrade Skill’s 56.3.

Where the 56.3 comes from

HVTrust dimensions vs the Agent Skills average

56.3 / 100 · 100.0% confidence

Claude Code Rails Upgrade Skill Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.0 / 25
1.0 below avg 8.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.7 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
19.8 / 20
5.7 above avg 14.1
AdoptionLog-scaled stars · package downloads
6.2 / 20
2.8 below avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-13
Rank Moved
Rank rose 11 spots (#156 → #145)
2026-10-03
Rank Moved
Rank dropped 12 spots (#137 → #149)
2026-10-01
Rank Moved
Rank dropped 11 spots (#124 → #135)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
71.3
Activity sub-score · out of 100
#149

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-15 04:08 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-10-15

Activity & Reach

Stars
392
Forks
19
Last Push
2026-10-12
3 days ago
Commits (4 wk)
288
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
9
Rank Change
▼1
was #148

Analysis

Activity Inputs

71.3 / 100
StarsRepository reach
15.6 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.0 / 20

Common questions about Claude Code Rails Upgrade Skill

Claude Code Rails Upgrade Skill has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Claude Code Rails Upgrade Skill publish package provenance?
No published build provenance is currently detected for Claude Code Rails Upgrade Skill. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Claude Code Rails Upgrade Skill have an OpenSSF Scorecard?
Claude Code Rails Upgrade Skill has an OpenSSF Scorecard score of 5.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Claude Code Rails Upgrade Skill actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Claude Code Rails Upgrade Skill use?
Claude Code Rails Upgrade Skill ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Claude Code Rails Upgrade Skill's commits signed?
12% of the last 100 commits to Claude Code Rails Upgrade Skill are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Claude Code Rails Upgrade Skill's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic

Maintain Claude Code Rails Upgrade Skill?

For maintainers

HVTrust scores Claude Code Rails Upgrade Skill from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 12Listed 2HVTrust 2Grade 2Scorecard 1Score 1Delisted 1Surface 1Surface 1
2026-10-13
Rank Moved
Rank rose 11 spots (#156 → #145)
2026-10-03
Rank Moved
Rank dropped 12 spots (#137 → #149)
2026-10-01
Rank Moved
Rank dropped 11 spots (#124 → #135)
2026-09-25
Rank Moved
Rank dropped 16 spots (#109 → #125)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 54 spots (#53 → #107)
2026-09-23
HVTrust Changed
HVTrust up 10.7pts (48.1 → 58.8)
2026-09-22
Newly Listed
First tracked at rank #53
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank rose 20 spots (#168 → #148)
2026-09-09
Activity Score Changed
Activity score up 8pts (44 → 52)
2026-09-05
Rank Moved
Rank dropped 14 spots (#140 → #154)
2026-08-31
Rank Moved
Rank dropped 14 spots (#102 → #116)
2026-08-30
Rank Moved
Rank dropped 18 spots (#84 → #102)
2026-08-29
Rank Moved
Rank dropped 15 spots (#69 → #84)
2026-08-28
Rank Moved
Rank dropped 16 spots (#53 → #69)
2026-08-27
Scorecard Added
OSSF Scorecard: 5.8/10
2026-08-27
Grade Changed
Trust grade D → C
2026-08-27
Rank Moved
Rank rose 178 spots (#231 → #53)
2026-08-27
HVTrust Changed
HVTrust up 32.7pts (20.3 → 53.0)
2026-08-26
Newly Listed
First tracked at rank #231

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/claude-code-rails-upgrade-skill.svg)](https://hvtracker.net/agents/claude-code-rails-upgrade-skill)
HTML:
<a href="https://hvtracker.net/agents/claude-code-rails-upgrade-skill"><img src="https://hvtracker.net/badge/claude-code-rails-upgrade-skill.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON