← back to leaderboard

hashicorp/vaultGitHub

https://github.com/hashicorp/vault
Stars:
36.4k
Language:
Go
Default branch:
main
Last scored:
5h ago
Overall

At a glance

Rank
#178 of 371
Top 48% · #23 of 37 Go repos
Checks passed
8 of 16
Full list below
Best set up for
Devin
Score 76.0
Needs most work for
Cursor
Biggest fix: Cursor rules (.cursor/rules) (+12.0 pts)

What it has

  • CI configuration
  • CONTRIBUTING guide
  • Dependency manifest
  • Reproducible dev env
  • License file

What it's missing

  • AGENTS.md / CLAUDE.md
  • .aider.conf.yml
  • Cursor rules (.cursor/rules)
  • GEMINI.md
  • .openhands/setup.sh

What to fix first

  1. 1
    AGENTS.md / CLAUDE.md
    Add an AGENTS.md covering project goals, layout, setup commands, and conventions. Aim for 800+ chars of real guidance (not boilerplate).
    +13.2 pts
  2. 2
    Pre-commit / git hooks
    Set up pre-commit (.pre-commit-config.yaml), husky, or lefthook to run format+lint on every commit.
    +5.3 pts
  3. 3
    Manageable size
    If possible, split into smaller modules or carve out a focused entry path. Document where to start in AGENTS.md.
    +5.3 pts

Score for each AI agent

Each agent looks for different things in a repo, based on its own docs. Under each score are the three checks it cares about most.

Devin
76.0
GPT-5 Codex
74.1
Claude Code
72.4
Kimi CLI
72.0
Pi
70.8
OpenHands
69.5
Aider
68.7
Gemini CLI
68.5
Cursor
68.3

Similar repos

Scored for Claude Code. Same language and host as this repo, scoring near it.

All Go repos →

All checks

AGENTS.md / CLAUDE.md· 0% pass
No agent instructions file found
.aider.conf.yml· 0% pass
No .aider.conf.yml at repo root
CI configuration· 100% pass
37 GitHub Actions workflow(s)
.github/workflows
CONTRIBUTING guide· 100% pass
Guide present
CONTRIBUTING.md
Cursor rules (.cursor/rules)· 0% pass
No .cursor/rules/*.mdc or .cursorrules
Dependency manifest· 100% pass
Manifest present
go.mod
Reproducible dev env· 100% pass
2 env artifacts (Makefile, Dockerfile)
Makefile
GEMINI.md· 0% pass
No GEMINI.md at repo root
License file· 100% pass
License present
LICENSE
Linter / formatter config· 100% pass
Config detected
.golangci.yml
.openhands/setup.sh· 0% pass
No .openhands/setup.sh
Pre-commit / git hooks· 0% pass
No pre-commit / husky / lefthook found
README· 100% pass
README detailed (12556 chars)
README.md
Manageable size· 20% pass
9338+ files — very large
Test suite· 70% pass
Test files detected (api/api_test.go)
api/api_test.go
Type configuration· 100% pass
Typed language (Go)

Add a badge to your README

Paste this at the top of the README. It shows the score, and links back to this page.

Agent friendly score for github/hashicorp/vault
[![Agent Friendly](https://agentfriendlycode.com/api/badge/github/hashicorp/vault.svg)](https://agentfriendlycode.com/repo/github/hashicorp/vault)

Check the score on every pull request

Add this file to your repo. On each pull request, it posts one comment showing how the score changed and why. It runs in your own CI, with no outside server involved.

# .github/workflows/agent-friendly.yml
name: Agent-friendly score diff

on:
  pull_request:
    branches: [main]

permissions:
  contents: read
  pull-requests: write

jobs:
  score-diff:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
        with:
          fetch-depth: 0
      - uses: hsnice16/agent-friendly-action@v0
        with:
          agents-badge-token: ${{ secrets.AGENTS_BADGE_TOKEN }}

Add AGENTS_BADGE_TOKENto the repo's secrets to turn the comment on. Without it, the action does nothing. Where do I add it?