Supported Stacks and Repository Types
Application stacks the platform recognizes, plus platform repository types such as Terraform and GitOps.
Application stacks
Readiness analysis is strongest when GitHub languages map to one of these application stacks:
| Stack | Typical languages |
|---|---|
| JVM | Java, Kotlin |
| iOS | Swift |
| Web / Node | TypeScript, JavaScript, React, Node |
| Go | Go |
| Python | Python |
If GitHub does not report a matching application stack, the platform can still Analyze the repository. Coverage then depends on repository type: a general checklist for unknown app layouts, or a platform profile when the repo is dedicated infrastructure.
The product does not list every supported language inside warning tooltips. Use this page (or Agentic Foundation → Supported languages in the app) as the source of truth.
Platform repository types
These repos are first-class scan subjects. They get a Platform repository badge and a reduced criterion set (many application criteria are marked not applicable):
| Type | What it usually contains |
|---|---|
| Terraform | Versioned *.tf, modules, remote state config |
| GitOps | Helm, Kustomize, Argo CD, or Flux manifests |
| CI templates | Reusable workflows or shared CI libraries. A service scan can read the repos you select and credit CI on change, CI runs build, CI runs tests, and CI static analysis. They do not credit CI ships artifact. See Linked platform repositories. |
| API contracts | Central OpenAPI / AsyncAPI / protobuf catalogs without an app runtime |
Platform type is detected from repository content (and optional linked platform repository settings), not from GitHub’s primary language alone. A warning that language-specific checks are skipped is normal for these repos.
A Terraform or CI templates repository can still get the Platform badge when the only application file is package.json or requirements.txt. A service repository that also contains OpenAPI, protobuf, or GraphQL stays a service. Those specs are still read for the API Contracts checks on that service.
Warnings vs ineligible
| Signal | Meaning |
|---|---|
| Warning (yellow) | Analysis can still run. Often means the repository’s languages are not scored in detail, it is a fork, or it includes languages outside that set. |
| Ineligible (orange, read-only) | Structural skip: archived, over size/count limits, or similar. Analyze and Fix stay disabled. |