// ecosystem support
What Drift can check in your stack
Support is not equally deep everywhere. Pick an ecosystem to see which checks run, what evidence Drift can collect, and where the gaps are.
DeepStrongWorkingLimited Full Partial None
Tap or hover a cell for the exact sentence.
| Ecosystem | Detect | Evidence | API surface | Static analysis | Find upgrades | Install a version | Verify | Fix | Automated PR |
|---|---|---|---|---|---|---|---|---|---|
JavaScript / TypeScript | |||||||||
Python | |||||||||
Go | |||||||||
Rust | |||||||||
Java / Kotlin / Scala | |||||||||
.NET | |||||||||
Elixir / Erlang | |||||||||
Dart / Flutter | |||||||||
Ruby | |||||||||
PHP | |||||||||
Swift | |||||||||
C / C++ (Conan) | |||||||||
C / C++ (vcpkg) | |||||||||
Arduino / PlatformIO | |||||||||
CocoaPods | |||||||||
OCaml |
- Deep — Drift computes the API diff from the published artefact, joins it to your code against module names the package itself declares, and can run the ecosystem's own build and tests over the result.
- Strong — Two of the three hold. Drift has a real answer here; one of the diff, the name resolution, or the verification is weaker than the others.
- Working — One of the three holds. Drift will tell you what moved and research it properly, and leaves more of the judgement with you.
- Limited — Detected, versioned, and researched. Whether it breaks your code is a question Drift cannot answer in this ecosystem.
The same breakdown, stage by stage, is in docs/support.md, generated from the same source.