Follow-up issue for static mix.exs support after the first mix.lock-only Hex parser lands.
Current status covered elsewhere:
- static parsing of
mix.lock
- extraction of locked Hex package versions, repos, checksums, managers, and nested dependency requirements
- explicit no-code-execution scope for the first Hex slice
Remaining work:
- decide whether a literal-only
mix.exs subset is useful enough to support
- extract top-level project identity and direct dependency declarations without executing Elixir
- define strict limits around dynamic expressions, module attributes, helper functions, env checks, and umbrella-specific patterns
Related umbrella issue: #341
Follow-up issue for static
mix.exssupport after the firstmix.lock-only Hex parser lands.Current status covered elsewhere:
mix.lockRemaining work:
mix.exssubset is useful enough to supportRelated umbrella issue: #341