The code already exists, so open-sourcing an internal tool can look almost free. Publishing is the cheap part. The liability begins when external users reasonably expect releases, answers, security handling, and migration guidance.
Source: [Dev.to](https://dev.to/bestbee/should-you-open-source-an-internal-developer-tool-price-the-maintenance-liability-dcj)