Using exact version constraint without boundaries are faling the validation about security-advisories HOT 5 CLOSED

Important to be noted that while single projects do not necessarily support x.y.z.w versioning, 8.7.4 is equivalent to 8.7.4.0.0, which does not include 8.7.4.1.0, for example.

from security-advisories.

@fabpot would the checkers (server-side and in the symfony binary) work properly with such constraint ? Or would it break existing tooling ?

from security-advisories.

@Ocramius probably also needs to check how the script that updates roave/SecurityAdvisories would handle these cases

from security-advisories.

I don't think that SecurityAdvisories can handle exact versions at this point in time, but I can most certainly adapt the code, given some time.

from security-advisories.

Source code is now open-source (https://github.com/fabpot/local-php-security-checker), so anyone is free to check the logic and provide a fix if needed. Let's close here.

from security-advisories.