Auto-generated — not yet edited · only the numbers are verified
- TESIGN / RADAR
- REPOSITORY CARD
- ifixai-ai/ifixai
ifixai-ai/ifixai
Independent Auditing of AI Agents. Run by human or the agent itself, to answer the most crucial question in the AI Agent Economy. Is the agent doing what is supposed to do? With iFixAi you can have this answer in less than 120 seconds.
RANKS Rising 7d #36 · Rising 30d #55
AT A GLANCE
- LANGUAGE
- Python
- LICENSE
- Apache-2.0
- USAGE
- Commercial use, redistribution OK. Keep notices; mark changes.
- ACTIVITY
- last commit 5 days ago ()
- TOPICS
- agent-evaluation
- ai
- ai-alignment
- ai-evaluation
- ai-governance
- ai-safety
- cli
- diagnostic-tool
- eu-ai-act
- hallucination-detection
- iso-42001
- llm-evaluation
- HOMEPAGE
- https://www.ifixai.ai
- REPOSITORY
- GitHub ↗
- CATEGORY
- AI
A summary, not legal advice.
README EXCERPT
iFixAi English · 简体中文 · 日本語 · 한국어 Independent Auditing of AI Agents Catch your agent's mistakes and blind spots before the shit hits the fan. Quick start • Three ways to run • Test your agent • Scoring • Docs • Contributing One ifixai run , end to end: guided setup picks the system, judge, and suite; the run verifies the connection and saves your config; 32 inspections execute across five pillars; and the result lands as an A–F grade with a scored core-pillar scorecard. --- What it is The existing Eval, Red-teaming, and Observability Tools are evaluating the agent mainly based on tech capability (token efficiency, latency, prompt injections). They cannot answer the most crucial question. Is the agent doing the job it is supposed to do based on the business KPIs and Organizational Structure? iFixAi gives you this answer in less than 120 seconds by striking the right balance between AI-Red Teaming and Operational Assurance. Adversarial depth. Assurance discipline. All-in-one auditing process. Three ways to run All three run the same diagnostic underneath. The difference is how you configure and drive it. CLI: guided wizard CLI: explicit flags Plugin or Skill --- --- --- --- How you d…
The opening of the GitHub README as stored, at most 1,200 characters. Markdown is not rendered.
TIMELINE
- Repository created
- Last push
- FIRST SEEN BY TESIGN
AI chooses the lists under the owner’s delegation. No human review is running in September 2026. Total stars, increases, cross-source signals, last updates and licences are shown as evidence. How ranks work →
If this repository gets editorial text (why, build, who, start, caveat) it becomes an edited entry. Until then the page shows only stored GitHub metadata and numbers.