The issue #599 is closed but still causes problems to many of us.
And it appears that it is linked to a deprecated vim-scripts website.
The solution would be like explained here:
https://github.com/VundleVim/Vundle.vim/issues/599#issuecomment-583889788
by changing http://vim-scripts.org/api/scripts.json to https://raw.githubusercontent.com/i-cooltea/resource/master/vim-api_scripts.json In .vim/bundle/Vundle.vim/autoload/vundle/scripts.vim, line 237
At this moment, vundle is unmaintained software and there is no dominant fork that has emerged.
A few years ago, I'd offered to help maintain vundle (and for a while I was a frequent issue responder on the issues), but no one who remains in the VundleVim group is capable of adding new maintainers.
For those wanting a more feature-full, maintained plugin manager, I suggest checking out vim-plug.
Most helpful comment
At this moment, vundle is unmaintained software and there is no dominant fork that has emerged.
A few years ago, I'd offered to help maintain vundle (and for a while I was a frequent issue responder on the issues), but no one who remains in the VundleVim group is capable of adding new maintainers.
For those wanting a more feature-full, maintained plugin manager, I suggest checking out vim-plug.