Skip to content

agent readiness score

rzp-slash[bot] edited this page May 5, 2026 · 2 revisions

Agent Readiness Score — razorpay/react-native-apollo-devtools

Scored by /agent-readiness-score. Band scale: <30 Not Ready | 30–54 Needs Work | 55–79 Assisted | 80+ Ready.

Last scored: 2026-05-06

Pillar Score /Max % Band
Context 4 /14 29% Not Ready
Testing 0 /30 0% Not Ready
CI/CD 0 /14 0% Not Ready
Aggregate 4 /58 7% Not Ready

Sub-criterion Breakdown

# Sub-criterion Score Max Key Evidence
C1 Agent-ready plugin outputs 0 6 20 failures — AGENTS.md, .agents/, .claude/ all missing
C2 Codebase navigability 4 4 100% — no qualifying subdirectories (≥15 src files); small lerna monorepo (26 files)
C3 Context freshness 0 4 No repo-skill docs with source/extracted_at frontmatter
T1 (UT) Unit test coverage 0 3 UT: 0% (no sonar-project.properties, no test framework configured)
T1 (SLIT) SLIT / integration coverage 0 6 SLIT: 0% (not onboarded to MCC)
T1 (E2E) E2E coverage 0 5 E2E: 0% (no E2E workflow or framework present)
T2 API & gRPC contract docs 0 5 NPM library (Apollo DevTools for React Native); no external API surface
T3 Devstack v2 readiness 0 5 No devstack — pure NPM package published via lerna; no Kubernetes deployment
T4 (Uptime) Devstack deployment SR 0 3 Uptime: no data (service not on devstack)
T4 (E2E SR) E2E test success rate 0 3 E2E SR: no data (no argo-workflows runs)
D1 Agent skill coverage in CI 0 4 No .agents/skills/; no .github/workflows/ in repo
D2 Deployment automation 0 4 spinacode: not found — NPM package, no Spinnaker pipeline
D3 CI speed & build hygiene 0 3 p50: N/A — no repo-owned CI workflows; only external platform checks (semgrep) run on PRs
D4 Take-it-live config 0 1 absent — no take-it-live.yaml
D5 Baseline-monitoring 0 2 metrics: no (no relevant backend surfaces detected), dashboard: no, alert: no

Summary

react-native-apollo-devtools is a small open-source NPM library (~26 files, lerna monorepo with one package) that provides Apollo DevTools for React Native — it is not a Razorpay backend service and has no Kubernetes deployment, CI workflows, devstack, or test infrastructure. The C2 score of 4 is a structural default (no large subdirectories to document), not a genuine signal of navigability. All other pillars score 0. The highest-leverage improvement for this repo would be adding a GitHub Actions CI workflow with at minimum a TypeScript build check and unit tests, since the lack of any CI means agents cannot validate changes or measure coverage.

Clone this wiki locally