I have a situation where some private repositories are being hosted in-house, which are required for a project.
I'm not allowed to provide access to those repositories for this module to utilize, and we want to avoid clogging our internal logging whenever the repository tries to update the report for these repositories.

Ideally, we'd like to tell the module (through yaml configuration) to ignore these repositories - either on a per-repository basis or, preferably, on a per-host basis so we can just ignore all of the repositories we host internally.

I'd be happy to submit a pull request if someone can point me in the right direction of where I'd need to make changes.

Accepance criteria

• PRs are re-targeted to CMS 5.
• There's a way to bypass or ignore private repos.
• Update note in Readme me to explain how to bypass private repos

PRs

• FIX Don't rely on inaccessible packages when fetching update info. #56
• ENH Allow developers to declare which packages are inaccessible. silverstripe-maintenance#170