Joris van Eijden

Composer uses PHP's [version_compare](https://www.php.net/manual/en/function.version-compare.php) which compares 2.0.0.beta.9 vs 2.0.0.beta.16. See [magento at packagist](https://packagist.org/packages/magento/community-edition#0.74.0-beta10) for example. see https://github.com/composer/composer/blob/0021758e0bcf964237a56cb22e2f0309118b6a3f/src/Composer/Package/Version/VersionSelector.php#L126

> > Next step is to prove directly that Composer sorts the list of versions differently to how we do. > > @back-2-95 ☝️ Somebody needs to confirm composer sorting,...

Rather than doing a `composer install` to generate a composer.lock file to analyze, with composer version 2 you can do a `composer update --no-install` to create just a composer.lock file...

The main question it needs to answer is: "**Why is this component included in this SBOM?**" My actual (way too frequent) scenario: - DependencyTrack says project X has a critical...

So when I change a variable in the web UI I also have to create an empty commit and push it in order for the change to be available to...

Same issue on Pop!_OS 20.04 LTS v13 systemd-resolve --status ``` Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting:...

Another problem is that the current code blows away any setgid from the parent dir.

I'm guessing this would solve my use-case too. I am currently unable to parse this: ``` f1 f4 41 20 73 65 6e 74 65 6e 63 65 3a f4...

> The first bump I hit was the unhandled CLTS command. I think I see enough info to figure out how to implement something simple like a register being cleared....

Are there any plans in motion for this?