Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for SRE, ops, and platform teams, AI agent developers, automation builders, AI-curious readers, and any developer wiring an AI coding agent to Kubernetes cluster investigation + reversible action -- and who can pair olemeyer/rocketplaneIO with Docker + a Kubernetes cluster (minikube is fine) for the runtime surface, an Anthropic- or OpenAI-compatible LLM (including a fully local, air-gapped
Who should use it
Who should skip it
Skip olemeyer/rocketplaneIO if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
olemeyer/rocketplaneIO is tracked by RepoRadar as a apache-2.0 self-hosted ai sre fo in the AI SRE for Kubernetes with Guardrail Catalog section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, olemeyer/rocketplaneIO is strongest on novelty (9.0) and workflow potential (8.8) and weakest on maturity (5.6) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned olemeyer/rocketplaneIO a composite score of 7.7 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The 122* / 0-fork repo is brand new (one week old) and at active maintenance but the status is alpha (developed against minikube; APIs and schemas still change without notice) -- do not point it at production yet; the guardrail catalog is ~30 named action pipelines but the consumer SHOULD review the list before relying on the action surface in a production cluster (the consumer SHOULD pin the olemeyer/rocketplaneIO version; audit the guardrail catalog.