A bug in the batch metadata synchronization task caused it to incorrectly evaluate whether a repository was private. The code previously relied on a private boolean field, which has now been updated to explicitly check the visibility string property from the API response instead. This ensures repository privacy settings are accurately evaluated and properly stored in the database.

Fixed detection of repository visibility during batch metadata synchronization - nom-social/nom