GSoC 2026: Question about Analyzer Plugin Resolution and analysis_options.yaml Lookup in Multi-Package Workspaces

[Zeba Fatma Akhtar Khan]

Hi everyone,

My name is Zeba Khan, and I'm a 3rd yr student and a enthusiastic Dart/Flutter developer interested in contributing to the Dart SDK and tooling ecosystem.

I recently came across issue #62690 (dart analyze and plugins not working when the base folder doesn't contain analysis_options.yaml) and the related issues #62686, #62451, and #62710. The problem — where custom analyzer plugins fail to run when dart analyze is invoked from a parent directory that lacks an analysis_options.yaml — is something I find both interesting and impactful for multi-package workspaces.

I'd love to contribute a fix or at least help investigate the root cause. I've reviewed the reproduction steps in the FMorschel/dependency_resolution repo and have some initial thoughts on where the analysis server context resolution might be going wrong.

A few questions to get oriented:
- Is there an existing owner or active investigation on this issue I should coordinate with?
- Are there any contributing guidelines specific to the analysis server / plugin loading code I should be aware of beyond the general Dart SDK contribution guide?
- Would a draft PR with an initial investigation be welcome at this stage?

Happy to start small — whether that's writing a test case, triaging related issues, or digging into the plugin loading logic in the analysis server.

Thanks for the warm welcome in advance!

Zeba Fatma Khan
https://github.com/zeba-source