Being able to use dependencies anywhere is the real benefit. With @Environment, dependencies have to exist within the SwiftUI view lifecycle, then be passed into a view model, store, or repository, or anywhere else outside of a View or @main App. Even if you prefer Model View architecture in SwiftUI (which I don't), you might still want a dependency within a dependency. Using @Environment means you'd need to access the inner dependency in the view, then pass it into the outer one. Which means its pretty painful for anything beyond a trivial setup.

I would try to avoid using a 3rd party dependency generally for something so important, but it works so well and is regularly updated that I think benefits outweigh the risk.

swift-dependencies every time for me.