Classic confinement request for dev-cli

Hello, Snap Store team!

I’m a Brazilian developer and I’d like to request classic confinement approval for my snap dev-cli.

I apologize in advance if there are any English mistakes — the project is currently only available in Portuguese, but internationalization is planned for one of the upcoming versions.


About the project:

dev-cli is a CLI tool designed to simplify the management of devcontainers. It acts as a wrapper that orchestrates tools already installed by the user on their system.

Why classic confinement is required:

The tool needs to invoke executables that are managed and installed directly by the user, such as:

  • devcontainer (often installed via nvm or other Node.js version managers)
  • docker / podman
  • Editors like VSCode, and others

These tools can be located in a wide variety of PATH locations depending on how the user chose to install them (e.g. nvm, Homebrew, custom directories). Because of this, strict confinement would prevent dev-cli from finding and executing these tools reliably.

Classic confinement is the only way to ensure dev-cli works correctly regardless of the user’s environment and installation preferences.

Thank you for your time and consideration!

This request has been added to the queue for review by the @reviewers team.

Hey @Brennon-Oliveira

Classic confinement is a sensitive matter and it is reserved for mature, well-known applications published by mature, well-known entities. I could not find evidences that dev-cli meets this criteria. Could you please point us to the correct sources (upstream repository, public documentation, etc.) if you think dev-cli meets that criteria currently?

Thanks