Sharepoint as a Custom Package Repository

I’m beginning to manage a larger number of employees that will be using Rhino and Grasshopper. Specifically, to run gh scripts and install plugins that my department is writing. It seems the Custom Package Manager is the best way to handle distributing the extensions that we’re using to write our scripts.

Our main file server is Sharepoint, but when I try to map my PackageManager.Sources to the Sharepoint http address, I get a 401 error.

Does anybody have any experience mapping their Custom Package Manager to Sharepoint for internal distribution?