pipe-cd / pipe-cd/pipecd

Your project is on the ACMM Leaderboard — see your AI-readiness score

Open
#6,707 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.4k
Forks
364
Avg merge
1d 4h
Merged PRs (30d)
84

Description

Hi! 👋

Your project currently appears on the ACMM Leaderboard — a public ranking of 289 CNCF & cloud-native projects scored by the AI Codebase Maturity Model, a 5-level framework (L1 Assisted → L5 Self-Sustaining) that measures how ready a codebase is for AI-assisted engineering.

See your full scan

👉 console.kubestellar.io/acmm?repo=pipe-cd/pipecd

The dashboard shows every detected vs. missing criterion, with an "Ask agent for help" button that launches an AI mission to add any missing one.

Add a badge to your README

Paste this in your README to show your ACMM level — it updates automatically as you add criteria:

[![ACMM](https://img.shields.io/endpoint?url=https%3A%2F%2Fconsole.kubestellar.io%2Fapi%2Facmm%2Fbadge%3Frepo%3Dpipe-cd%2Fpipecd)](https://console.kubestellar.io/acmm?repo=pipe-cd%2Fpipecd&utm_source=github&utm_medium=badge&utm_campaign=acmm-outreach)
Why it matters

Projects with higher ACMM scores get measurably better AI-assisted PRs because the agent has rules, tests, and metrics to work against. The badge signals to contributors (and AI agents) how much scaffolding is in place — a way for smaller projects to compete on AI-readiness without needing massive contributor counts.

The leaderboard

See where you rank among 289 projects: kubestellar.io/en/acmm-leaderboard

Paper: arxiv.org/abs/2604.09388

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source file or test and is promotional rather than an implementation request. If treated as documentation work, start by reviewing README.md and determine whether the proposed ACMM badge belongs there; done would require a clear maintainer decision and any agreed README change.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.