PageSourceSearch

https://oobeya.io/_nuxt/CjbM8Ery.js

js oobeya.io collected 2026-10-03 20:54:05 UTC 1,474 bytes, 1 lines download raw bytes

1import{_ as t}from"./Bb4eqU7i.js";import{u as o}from"./DYGLacVr.js";import{e as n,o as i,q as s}from"./DlpDSASA.js";const p=n({__name:"BlamelyGitAiComparisonFaqSection",setup(r){const e=[{question:"Is Blamely AI an alternative to Git AI?",answer:"Yes. Blamely AI can be evaluated as a Git AI alternative when teams need AI vs. human code attribution with enterprise support, governance, richer context, and Oobeya analytics."},{question:"Where can Git AI fit well?",answer:"Git AI may fit teams experimenting with an open-source approach to AI code attribution and Git notes based workflows."},{question:"How does Blamely AI connect with Oobeya?",answer:"Blamely AI captures code-origin and AI attribution signals, while Oobeya connects those signals with pull requests, review behavior, quality, delivery, team metrics, and broader engineering outcomes."},{question:"Can teams measure the impact of AI-generated code?",answer:"Yes. Blamely AI and Oobeya help teams analyze AI-generated and AI-assisted code alongside rework, review, code quality, security findings, delivery flow, and team-level outcomes."},{question:"Which should a team choose?",answer:"Choose Git AI for lightweight open-source experimentation. Choose Blamely AI with Oobeya when attribution needs to become part of a governed team or enterprise engineering analytics program."}];return o(e),(c,l)=>{const a=t;return i(),s(a,{"comparison-name":"Blamely AI vs Git AI",items:e})}}});export{p as default};

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.