Hi. So, you can remix, right? And, remixing is essentially… copying someone elses project and then tweaking it. But.. some people steal. And stealing is bad. So, heres a solution for it:
If Scratch detects a user not tweaking ANYTHING or something very minor, like changing a costume by adding 1 pixel, or changing the brightness by 1, then it will not allow them to share the project, unless they tweak it enough.

This is very short, but it would fix most stealing thingies.

Bye

define: enough

The Informal and Unofficial List of Rejected Suggestions wrote:

3.2 Disable remixing or censor minor remixes
One of the most important ideas of Scratch is the share aspect. Scratch is a website not only for displaying your work, but also for sharing it with others, and by posting your project on the Scratch website you agree to allow others to remix your work. This includes allowing others to use the backpack to use your creations in their own projects. You are not allowed to ask others not to remix your projects; you may get alerted for this, because it discourages remixing. This extends to the ability to require permission to remix a project, as you have already given permission to others to use your creations by sharing a project on Scratch; for more information, see this post.

That aside - I should mention that every project is under CC-BY-SA 2.0; this would actively go against the brief summary given:

This license enables reusers to distribute, remix, adapt, and build upon the material in any medium or format, so long as attribution is given to the creator. The license allows for commercial use. If you remix, adapt, or build upon the material, you must license the modified material under identical terms. CC BY-SA includes the following elements:
BY: credit must be given to the creator.
SA: Adaptations must be shared under the same terms.

Though this is the description for 4.0 and Scratch, as far as I am aware, still uses 2.0, it boils down to roughly the same terms (EDIT: Well, the part that matters here, anyways). You can read them here.

It should be of note that this freedom explicitly is irrevocable unless the license's terms are breached.

For clarity, I recommend reading the entire legal code.

7. Termination

a. This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms of this License. Individuals or entities who have received Derivative Works or Collective Works from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.

b. Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above.

This idea goes back many years! Here's a quote from a post from 2015

Paddle2See wrote:

We've had several discussions about ways to better insure that remixes are “valid” - but it's not an easy thing. Having an automatic check that looks to see if *any* change has been made should be possible (and that would be a big help by itself!) but moving beyond that things get complicated and may require human intelligence and judgement. Trying to spell out how many pixels need to change on a costume - or how many scripts need to change - seems pretty unrelated to how much creativity or thought went into the remix. Which brings us back to where we are today - use the Report button if no changes have been made.

Since that topic (and others) dealing with the same idea has been closed (because the idea is already known to the Scratch Team - just hasn't proven feasible to implement yet), it makes sense to close this one as well.