Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for security and platform teams running AI coding agents (Claude Code, Codex, OpenCode, Hermes, custom harnesses) on a fleet of developer endpoints who need long-horizon runtime safety and audit, not a one-shot pre-tool hook: Gensee Crate is the Apache-2.0 alpha sidecar that watches system events, user requests, tool calls, skills, and memory across requests and sessions; for security teams
Who should use it
Who should skip it
Pass on GenseeAI/gensee-crate if you need something non-technical and turnkey rather than a tool that requires comfort with CLI, dependencies, or system configuration.
About this signal
GenseeAI/gensee-crate is tracked by RepoRadar as a full-stack, long-horizon runtime in the Apache-2.0 alpha full-stack runtime safety sidec section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'try now' with a Silver tier and hard setup difficulty. Across RepoRadar's eight signals, GenseeAI/gensee-crate is strongest on workflow potential (8.9) and open-source/build quality (8.4) and weakest on setup ease (4.2) — 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 GenseeAI/gensee-crate a composite score of 7.8 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 54.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.
Risk explanation
**Alpha status: the API and policy schema are still settling.** The README's alpha-status badge is the maturity signal to read first — the sidecar is in alpha, so the API and the policy schema can change between versions. Pin to a specific commit or release tag for any production-pilot evaluation, and budget for a small migration between alpha versions; **macOS-first: Linux and Windows support is on the roadmap, not the first evaluation target.** The macOS-first platform badge scopes the current evaluation target. Fleet deployments on Linux or Windows endpoints will hit the platform-first story — read the roadmap and confirm the timeline before committing to a non-macOS pilot; **Enterprise tier is a paid offering — review the contract terms before committing.** The README links to a contact page for the enterprise tier with company-enforced rules, credential and identity controls, and oversight across a distributed fleet. The Apache-2.0 sidecar is the right starting point for a pilot; the enterprise tier is a separate paid contract. Read the enterprise contract terms (data handling, SLA, support, multi-tenant isolation) before committing any production deployment to the enterprise tier.