Proposal: Public API Audit and 1.0 Stabilization Approach

[Chaitanya-Parab]

Hi everyone 👋

I’m Chaitanya, a front-end developer currently exploring Rust and systems programming. I’m interested in contributing to Boa for GSoC 2026, specifically around the Public API Audit and 1.0 Stabilization effort (#4524).
I wanted to share my proposed approach and get feedback before starting implementation.

Proposed Approach

I plan to audit Boa’s public API surface module-by-module and identify areas that could lead to future breaking changes.
Specifically, I would focus on:

• Replacing public struct fields with private fields and exposing them via getter methods where appropriate.
• Adding #[non_exhaustive] to public enums/structs that may need future extensibility.
• Reviewing visibility and reducing unnecessary pub usage.
• Improving documentation for public-facing APIs.

Execution Plan

• Start with smaller, self-contained modules.
• Submit incremental PRs.
• Document API design decisions and trade-offs along the way.

Request for Feedback

Does this approach sound reasonable?
Also, are there specific modules that would be good starting points for the API audit?

Thanks!
Chaitanya Parab