:mag: ScanCode detects licenses, copyrights, dependencies by "scanning code" ... to discover and inventory open source and third-party packages used in your code. Sponsored by NLnet project https://nlnet.nl/project/vulnerabilitydatabase, the Google Summer of Code, Azure credits, nexB and others generous sponsors!
This is misleading as the rule might have changed when the report has been generated with an older ScanCode Toolkit version or even deleted, thus making the reference more or less obsolete/fragile.
System configuration
What OS are you running on? Linux
What version of scancode-toolkit was used to generate the scan file? 32.1.0
What installation method was used to install/run scancode? pip
@stefan6419846 good point!
We have since then evolved a rule to deprecate but never delete or repurpose existing rules.
But pointing to a specific tag or commit would be a good thing.
Description
In the generated YAML report, the rule URL refers to the
develop
branch instead of the tagged release if used from a release.How To Reproduce
Running
scancode -l --license-text setup.py --info --url --copyright --yaml setup.yaml
on a file generates a YAML report which includesThis is misleading as the rule might have changed when the report has been generated with an older ScanCode Toolkit version or even deleted, thus making the reference more or less obsolete/fragile.
System configuration