AI coding tool adoption has surged. Confidence in the software those tools produce has not.
Developers increasingly report shipping code they do not fully understand, and spending more time than expected debugging AI generated output. But the enterprise question is larger than whether a single function works.
Can an organization understand, govern, change, secure, and sustain AI generated software at scale?
That is a question of software readiness.
To test readiness where the technology should be most mature, we assessed public repositories maintained by organizations building frontier AI models. These teams have exceptional access to AI capability, talent, and infrastructure. If readiness gaps appear in the code they publish, the challenge extends beyond any one team’s engineering discipline.
Using ForgeScore, an eight dimension software readiness assessment, we evaluated 83 public repositories from 29 leading AI organizations as published in August 2026.
The results are not an indictment of any one lab. They reveal a shared industry constraint. AI can accelerate code production, but it does not automatically create software that is easier to understand, govern, secure, or sustain.
Scope and methodology
Benchmark scope
ForgeScore was applied to 83 publicly available repositories maintained by 29 AI model organizations. The benchmark covers code each organization chose to publish. It does not evaluate private repositories, internal systems, or overall engineering performance. All scores reflect repositories as they appeared in August 2026.
What ForgeScore measures
ForgeScore rates a codebase out of 100 from a lead architect’s perspective. It evaluates eight weighted dimensions.
| Code Excellence | Future Proofing |
| System Gravity | Semantic Clarity |
| Cognitive Load | Data Weight |
| Logic Narrative | Trust Boundaries |
| Weak | Moderate | Strong |
| 0 – 40 | 41 – 74 | 75 – 100 |
Scores of 75 or higher are strong. Scores from 40 to 74 are moderate. Scores below 40 are weak. The frontier average of 74.6 lands just under the strong threshold.
Finding 1: Frontier access does not eliminate software complexity
Across the 83 repositories, the average ForgeScore was 74.6. The highest organization level score was 78.6, recorded by OpenAI. No organization reached the 80s.
Scores ranged from 67.0 to 78.6, a spread of 11.6 points across 29 organizations with different engineering cultures, review practices, resources, and access to frontier technology.
The important result is not who ranked first. It is that no organization crossed into the 80s.
The frontier’s best models, engineers, and compute resources have not eliminated the underlying challenge of building software that remains understandable and manageable as it evolves. AI can generate more code, faster. It does not inherently make that code easier to modify, govern, secure, or operate over time.
For enterprises, the question is not simply, “Can AI produce working code?” It is, “Can we confidently accept, govern, and sustain what it produces?”
Finding 2: The weakest link is trust, not code generation
| 71.1 Trust Boundaries | Lowest of eight ForgeScore dimensions 3.5 points below the 74.6 overall composite average |
| Trust Boundaries was the lowest scoring ForgeScore dimension across the benchmark, averaging 71.1 versus a 74.6 overall composite average. |
Trust Boundaries evaluates the controls around authentication, authorization, secrets management, exposed interfaces, service edges, and data access. These are the areas where risk enters a system, spreads across dependencies, and becomes harder to detect after software is deployed.
Examples from the public repositories assessed included the following.
| Organization | What the assessment found |
| Meta | Repositories containing API keys in Android client code, accompanied by a comment acknowledging the exposure. |
| DeepSeek | Repositories exposing inference endpoints without built in request throttling or rate limiting. |
AI increases the volume and velocity of software change. Without clear specifications, safeguards, and governance, it can also accelerate the introduction of security exposures and operational debt.
| Working code is not necessarily trustworthy code.A system can compile, pass tests, and appear complete while still being unsafe, opaque, or difficult to operate in production. |
What this means for your codebase
The exposure may be deeper than it appears
If Trust Boundaries are a weak point in repositories maintained by frontier AI organizations, enterprise codebases may carry greater hidden exposure. Most are older, more interconnected, and subject to less continuous scrutiny.
Debt needs a measurable baseline
Technical debt is difficult to prioritize when it remains abstract. A ForgeScore creates a measurable baseline that teams can track over time, use to guide investment, and communicate to executives and boards.
Speed can outpace scrutiny
When software changes faster than teams can understand and validate it, each accepted change can lower the baseline for the next. AI generated code can then compound on top of unexamined assumptions, unclear architecture, and inherited risk.
The frontier’s lesson: AI speed requires context and governance
AI is not the constraint. Software readiness is.
The frontier AI labs show that even organizations closest to the technology can accelerate development without fully solving for maintainability, security, clarity, and governance. Their public repositories reached the high 70s on ForgeScore, but none reached the 80s, and Trust Boundaries remained the weakest dimension.
For enterprises building new applications or modernizing decades of legacy software, the lesson is clear. AI speed without context, control, and governance accelerates complexity.
| Context | Specifications | Orchestration | Governance | Production |
Forge gives AI the context, specifications, orchestration, and governance needed to turn AI assisted development into enterprise ready software, whether that software is newly built or shaped by years of legacy decisions.
How ready is your software for AI?
Benchmark your codebase against the same dimensions used in the Frontier AI Software Readiness Benchmark.
Identify where complexity, maintainability, security, and trust boundaries could limit AI accelerated development or modernization.
