#Script started out as an alternative to Razor Pages [1] (where it was initially called ServiceStack Templates [2]) to give ServiceStack Apps a productive alternative to Razor for developing server-driven Web Apps, but as it's highly extensible without external deps or reliance in external tooling it was easy to re-purpose as a dynamic emeddable language to be able to basically script any .NET App, hence the rebrand to a stand-alone #Script language, all the whilst its implementation remained in the core ServiceStack.Common assembly. If it becomes an issue we can look at pulling it out of the main ServiceStack repo in a stand-alone repo with a weaker copyleft OSS license, but it would require a bit of work and would need to ensure it's not disruptive to existing ServiceStack Customers, I just didn't expect there to be any issue for a gratis library that's also OSS.
Incidentally the ServiceStack.Glue library that the Desktop Apps use to embed .NET Core Apps in a Chromium Desktop Shell is MIT [3].
[1] https://sharpscript.net/docs/sharp-pages