StackBlitz‑GitHub Import: Default Visibility Decision for Private Repositories

When importing a GitHub repository via StackBlitz’s Import from GitHub button, the platform creates a StackBlitz project whose visibility is public by default, requiring the user to manually enable the Private project option during import.

This behavior poses a risk of accidental exposure for private repositories, especially in team workflows where developers may overlook the visibility toggle.

The goal is to determine whether StackBlitz should automatically align the visibility of the imported project with the source repository’s privacy setting to reduce unintended disclosure.

Uncertainty remains about the impact on existing public projects, the clarity of the UI prompt, and whether changing the default would affect users who rely on public projects for sharing.

Should StackBlitz automatically set the imported project to private when the source GitHub repository is private?
How can the import UI be adjusted to make the private option more conspicuous without disrupting current workflows?
What migration strategy, if any, should be applied to already‑imported public projects if the default behavior changes?