Gitlab/Bitbucket support

[SkeLLLa]

Hello. Are there any plans to support Gitlab or Bitbucket? Now packages hosted on these sites will receive less score by default because of parser, not because of their actual quality.

[satazor]

When npms-analyzer was created, the Bitbucket and Gitlab APIs to fetch information were very raw and provided little to zero useful information as compared to GitHub.

Need to investigate if Gitlab/Bitbucket APIs evolved.

[ramiel]

Even if this analyzer is not capable of getting information from gitlab/bitbucket, this doesn't explain why a package which is not hosted on github is penalized.

[CarbonCollins]

Has this been followed up since the last message?

GitLab v3 API was deprecated and then removed on 22nd June 2018 in there v11 release.

I don't use BitBucket myself but I do believe they are also deprecating there older APIs at some point this year

[SkeLLLa]

As far as I know it's just not implemented. So there are no problems with API deprecation when it not uses that API :)

[CarbonCollins]

Ah I was more implying that there have been changes to the API since @satazor comment. After re-reading my comment I realised that I did not make that very clear.

[zypA13510]

While looking into the way npms-analyzer analyze badge count, I discovered that the library used, detect-readme-badges, would only detect badges for projects on GitHub (at least for some type of badges).
Also, from what I've seen, the list of badges it can detect is quite limited. Namely, GitLab CI will not be detected, which I suppose those who use GitLab will likely be using. This means packages not hosted on GitHub can still be penalized even if we fix the API calls here.

Just something to consider if someone decides to take on this.

[JacoKoster]

Hi 👋🏼 It's 2023 now and packages are still penalized for using GitLab. Is there anything we can help out with to make this move along?