I ran Alizer via the command line for a number of Git repositories, and it failed to detect ports in all of them, for varying reasons.

1. For a sample node project: It failed because it can’t handle port declarations like var PORT = process.env.PORT || 8080. It expects something like var PORT = 8080
   • Ideally alizer would be able to handle this scenario too as it seems to be a relatively common convention in nodejs projects
2. For a Go project: It can only handle certain frameworks, and Burr’s repo wasn’t using any specific REST framework.
   • Alizer can handle a number of different Go REST frameworks (e.g. Go-Gin), but it can detect ports that are just using Go's built in net/http web server
3. For Quarkus and Spring Boot projects, there isn’t anywhere in the source code where the port is defined explicitly, and alizer doesn’t make any “assumptions” about default ports it seems (edited)
   • Does alizer benefit from returning the default port (8080) in this scenario? Or should it still return nil?

Update: @thepetk
Target date: 28 Apr 2023