So if you happen to insert invalid version string when requiring package, it will still write it into composer.json and nothing works after that. So for example; composer require phpunit/phpunit:"8.3.3 as ^8.3"

My composer.json:

{
    "require": {
        "phpunit/phpunit": "8.3.3 as ^8.3"
    }
}

Output of composer diagnose:

$ composer diagnose
        

Description

Running the following command:
./scancode -clpieu --json-pp facet_summary.json samples --summary --facet dev=*.java --summary-by-facet

Generates the following Error

ERROR: failed to run post-scan plugin: summary-by-facet:
Traceback (most recent call last):
  File "/home/ayansm/Desktop/GSoD/scancode-toolkit-versions/scancode-toolkit-3.1.1/src/scancode/cli.py", lin

Deleting a status message doesn't require a confirmation. All destructive actions should require confirmation to prevent user errors.

As you can see in the screenshot above, clicking on the delete icon should trigger a confirmation modal. We already have a few modals doing e

Some packages may bundle dependencies. We could report outdatedness for these the following way: for outdated packages with single download, propagate outdated status onto the download URL. Then we could show this download specially for other packages, or even make it affect the status.