propel: 2.0.0-alpha11 about security-advisories HOT 11 CLOSED

Propel alpha is sadly very widespreadly used, so it's probably stable software that is not declared as such.

IMO valid to notify users that they are running something harmful.

from security-advisories.

The whole code is now Open-Source at https://github.com/fabpot/local-php-security-checker (server + client code, so no more API calls). Feel free to submit a PR there to fix this bug.

from security-advisories.

We should not have entries for alpha versions IMHO.

from security-advisories.

@thirdender as this targets composer packages, it should support things that composer accepts.

from security-advisories.

Related: Roave/SecurityAdvisoriesBuilder#98 - @slash3b worked quite a lot to add support for patch version modifiers, should you need inspiration.

from security-advisories.

It looks to me like the security-advisory lists the correct versions, but the tool you're using doesn't understand the "-alphaX" portion of the version string. I think an issue needs to be raised for the symfony/cli repo to address the tool that is parsing the version strings.

from security-advisories.

The false positive is still present though it seems - the source of the problem seems still to be that the tool cannot properly see the order of non trivial release versions, e.g. alpha, beta, RC:

2.0.0-alpha1 < 2.0.0-alpha11 < 2.0.0-alpha2

the tool thinks - which is incorrect.

from security-advisories.

I think I'm in agreement with @fabpot that there should not be any alpha/beta/rc identifiers. The SemVer spec does not consider these pre-release tags when comparing versions. See https://interrupt.memfault.com/blog/release-versioning for a good write-up of SemVer. Ideally the Propel2 library should increment the patch version number and not the "alpha" number.

from security-advisories.

semver definitely considers pre-release tags. But the official semver spec requires a . between the prerelease identifier (alpha) and the prerelease version (so 2.0.0-alpha.11).

from security-advisories.

Hmm, the article and SemVer library I'm using are both wrong then. Thanks for digging that up, looks like I have some more research to do.

from security-advisories.

I opened fabpot/local-php-security-checker#9 on the checker project itself to track this, in case someone wants to contribute.

from security-advisories.