Mirrored Packages

Some packages on Forest carry a Mirrored badge. These are packages imported from Wally , brought over so the ecosystem’s existing open-source libraries are installable from day one.

Wally is a Roblox package manager, so mirrored packages are a Roblox-only concept.

What “Mirrored” means

The source is unmodified. A mirrored version contains the exact files its author published to Wally.
Only open-source packages are mirrored. A version is imported only when it declares (or ships in its archive) a recognized open-source license, and it gets the same license safety rating as any other package. Each version’s license notes state exactly where its license came from.
The scope is reserved, not owned. Mirrored packages have no Forest account behind them yet. The author’s scope name is held in reserve so nobody else can register it. That’s why the byline isn’t a profile link.
The mirror stays current. New Wally releases of a mirrored package appear on Forest automatically, and packages removed upstream are removed here too.

Using a mirrored package

Install it like any other package:


forest i evaera/promise

Dependencies, version ranges, the lockfile, and integrity checks all behave exactly as they do for native Forest packages.

Mirrored packages that have dependencies include a few small generated .lua link files alongside the original source. Wally arranged installed packages differently on disk, so these links let the package’s internal requires resolve inside Forest’s Packages layout. They’re part of the published archive and covered by the same integrity hash as everything else.

Server-realm packages from Wally

Wally had a “realm” concept (separate server and shared dependency lists); Forest deliberately does not. There is one Packages tree and you decide where it mounts. If a mirrored package was server-realm on Wally (anti-cheat, server frameworks), install it from a server-side manifest using the two-manifest pattern so it never replicates to clients.

Claiming your scope

If you published these packages on Wally, the scope is being held for you, and you can claim it now. You claim a scope by verifying the same GitHub identity that owned it on Wally: link that GitHub account to your Forest account, then claim the scope from your account settings (or, if the scope name matches the account you’re signing up as, verify inline during registration). Once claimed, the packages become yours to manage like any other Forest packages, and future Wally releases keep mirroring in. A Studio can claim a scope too; an admin or owner verifies with their own linked GitHub.

If you need something changed or taken down that a claim doesn’t cover, reach out through forest.dev .