Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison of release dates does not work as intended #199

Open
thaljef opened this issue Nov 8, 2021 · 0 comments
Open

Comparison of release dates does not work as intended #199

thaljef opened this issue Nov 8, 2021 · 0 comments
Labels
Client Issues relating to blackduck.Client examples An issue related to an example script

Comments

@thaljef
Copy link
Contributor

thaljef commented Nov 8, 2021

At line 122 of get_upstream_copyrights.py, the releasedOn attribute is copied from the BOM component version. It is later used for comparison at line 127:128 to determine if the other component is newer. However, the releasedOn date for a BOM component version seems to always be the date of the scan that detected the component, rather than the release date of the underlying component version. I don't know if that is the intended behavior of the API, but it sure seems suspicious. Either way, the code written here doesn't work as intended.

@OffBy0x01 OffBy0x01 added examples An issue related to an example script Client Issues relating to blackduck.Client labels Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client Issues relating to blackduck.Client examples An issue related to an example script
Projects
None yet
Development

No branches or pull requests

2 participants