You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
In UI and API, sort packages and vulnerabilities from newest to oldest. #1754
When I use the UI and search for packages, or when I use the API, I would like to see results of package lists sorted by version from newest to oldest. Same for vulnerabilities, from newest to oldest.
Why? because I am more likely to be interested by recent and current versions than older versions and older vulnerabilities.
changed the title [-]In UI and API, sorts packages by version from newest to oldest, and vulnerabilities too[/-][+]In UI and API, sort packages and vulnerabilities from newest to oldest.[/+]on Jan 21, 2025
Hi @pombredanne , I have made some changes and testing them on my local server I have firstly imported some packages and vulnerability data and then runned python3 manage.py improve compute_version_rank imporover in order to assign the the version ranking to the packages.
After that I have impletelemented some changes in the views.py (https://gist.github.com/Rishi-source/25e42438c87c26c3b7d1324bba60609f) and I have got these results I am sharing a screenshot of the ordering of the results after implementing these changes which I have provided in the gist.
Please correct me If I am wrong at some point. I also want to ask that have I correctly sorted the vulnerability data on the basis of vulnerability_id or I have to use/make some other field in order to sort them.
I was exploring this issue and noticed that there have already been some discussions and attempts to implement sorting.
Is this issue still open for contribution, or is there any remaining part that I could help with?
I would be happy to contribute if there is still work needed.
Thank you!
Activity
[-]In UI and API, sorts packages by version from newest to oldest, and vulnerabilities too[/-][+]In UI and API, sort packages and vulnerabilities from newest to oldest.[/+]atmajaa commentedon Jan 22, 2025
@pombredanne Hi, I am working on this issue. Will update if I have any doubts!
pombredanne commentedon Jan 22, 2025
@atmajaa Thanks! please make sure to start by outlining the gist of your design as a comment.
Rishi-source commentedon Jan 23, 2025
Hi @pombredanne , I have made some changes and testing them on my local server I have firstly imported some packages and vulnerability data and then runned
python3 manage.py improve compute_version_rankimporover in order to assign the the version ranking to the packages.After that I have impletelemented some changes in the views.py (https://gist.github.com/Rishi-source/25e42438c87c26c3b7d1324bba60609f) and I have got these results I am sharing a screenshot of the ordering of the results after implementing these changes which I have provided in the gist.
Please correct me If I am wrong at some point. I also want to ask that have I correctly sorted the vulnerability data on the basis of vulnerability_id or I have to use/make some other field in order to sort them.
topslugBurpy commentedon Feb 11, 2025
hey @pombredanne is this issure resolved?
nadhamsaipallavi commentedon Mar 20, 2025
hello i want to contribute to this issue , can I ?
shivamshrma09 commentedon Feb 5, 2026
Hi @pombredanne!
Want to fix
#1754 (newest-first sorting).
Know Django, local Docker running.
PR ready in 2 days!
fix aboutcode-org#1754: newest-first sorting for packages + vulnerabi…
shivamshrma09 commentedon Feb 5, 2026
good evening
@pombredanne sir
i have made an PR to resolve this issue plz review it
i like Aboutcode org Projects bcz it resolve real issues faced by Devlopers
fix aboutcode-org#1754: newest-first sorting for packages + vulnerabi…
Raji2006629 commentedon Mar 19, 2026
Hi, I'm interested in working on this issue. Is this still relevant and available?
fix aboutcode-org#1754: newest-first sorting for packages + vulnerabi…
ashwinraj8090 commentedon Mar 28, 2026
Hi @pombredanne,
I was exploring this issue and noticed that there have already been some discussions and attempts to implement sorting.
Is this issue still open for contribution, or is there any remaining part that I could help with?
I would be happy to contribute if there is still work needed.
Thank you!
ziadhany commentedon Jul 14, 2026
This issue has been partially fixed:
see: