Publishing rules

1. Before you publish#

The publish step runs these checks, in this order: Compiles, Declares FORGE_API, Runs on the standard symbols, No look-ahead, Chart and engine agree, No secrets in the source, No network or blocked imports, Enough trades, Not a near copy, Has a description and Has tests. A failed required check stops the publish and says why.

2. The publishing rules#

Every script published to the Forge library.

No harmful code

A script must not try to reach the network, read or write files, escape its sandbox or harm anyone who runs it.

Forge compute is for testing

Do not use Forge compute for mining, servers, remote access or anything other than testing trading ideas.

No profit promises

Titles and descriptions must not promise profit, call a result guaranteed or use sensational claims.

Describe it honestly

Say what the script does and how to use it. Do not misstate what it does or what its tests show.

Credit and real changes

A script built on someone else's open script credits it and changes it in a real way, not only its name or colours.

3. Credit and real changes#

A script built on someone else's open script names it and changes it in a real way. A new name or new colours is not a real change. Forge compares every script with the ones already published. A close match is flagged for a person to look at and is never refused on that alone.

4. No profit promises#

Titles and descriptions may not promise profit or use sensational words. Forge checks every listing for these words before it publishes:

• guaranteed
• guarantee
• risk-free
• risk free
• no risk
• can't lose
• cannot lose
• never loses
• 100% win
• sure profit
• sure win
• get rich
• holy grail
• money machine
• free money
• double your account

5. Enough trades on realistic costs#

Forge tests every published strategy itself, on the same standard setup for everyone, with the costs of a named broker profile (see the standard setup). A strategy is published only when Forge's check run makes at least 300 trades. Below that on the standard setup, its listing says Too few trades.

6. Who sees your code#

Open shows the code to everyone, Protected shows only what the script does, and Unlisted is reached by its address. A protected or unlisted script keeps all rights.

7. Protected scripts#

A protected script runs on Forge's servers. People who use it get its results and never its code. If it fails for them, they see only its error code, and you see the full error.

8. Licences#

The licences an open script can carry are on the licences page.