How to build services for FOSS projects when ToS forbids scraping?

I'm working on a service for FOSS developers to help enforce code license compliance and make projects more sustainable.

The challenge: many websites' Terms of Service explicitly prohibit scraping, crawling, or automation. At the same time, the information needed (repos, dependencies, metadata) is often available only through those sites.

For those who've built tools around open source ecosystems:

* How do you navigate ToS restrictions while still delivering value to users?

* Do you focus on official APIs only, even if they're limited?

* Are there established legal/technical best practices for this situation?

* How to balance compliance with ToS and the mission of supporting FOSS?

Curious to hear what others have done (or seen work) in this space.