As suggested by @Pcoombe in one of our first advisory board meetings, we may have a special type of transformation step that pulls its implementation from a collaborative repository of community-curated transformation functions.

Such a transformation step may have its configuration value set to the path from which the community-defined implementation should be retrieved.

A workaround may be implementing a custom-JavaScript transformation step (T305883), but that would lack the capability of maintaining the code in one place, without having to change all translation templates that use it.

Because this would be running custom JavaScript code, the same security considerations as in T305883 should be taken into account.