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
fast-scan: Create scan benchmark for package detection in ScanCode Toolkit #4061
The package detection benchmark should be based on real case and not made up data. We should have at least a package for each type, and cases with and without nested package files, deep dependencies and complex licensing.
@AyanSinhaMahapatra I have created a list that could potentially used as the benchmarks for package scan. Please take a quick look to see if it's alright and I'll do the download and launch the package scan.
@AyanSinhaMahapatra you said you have a script to run scans, and get summaries and look for issues with --todo , feel free to let me know if I can help with anything
I could not finish the scans as I was looking to run the scans inside somekind of timeout using src/scancode/interrupt.py (for the package assembly step) so we are not stuck there. I still have to update the script and rerun this so we finish scanning all the packages here.
At some point of time, creating a pipeline can work too.
Activity
AyanSinhaMahapatra commentedon Feb 28, 2025
Related issues:
inspect_packagesand other pipelines is too slow scancode.io#1398... therefore package "assembly" is a likely candidate
chinyeungli commentedon Jul 18, 2025
fast-scan-package_scans_benchmark-list.csv
@AyanSinhaMahapatra I have created a list that could potentially used as the benchmarks for package scan. Please take a quick look to see if it's alright and I'll do the download and launch the package scan.
chinyeungli commentedon Jul 30, 2025
@pombredanne please check fast-scan-package_scans_benchmark-list.csv
(Also at
https://docs.google.com/spreadsheets/d/1A4g6LvP1s-DuBI1_Ev_hJuQ81bTTkMzL/edit?usp=drive_link&ouid=111292578521869099532&rtpof=true&sd=true )
if these are the things that we want to look at. There are basically 3 items that I look at:
Since these tasks are entirely manual, perhaps doing a few of each type is sufficient?
chinyeungli commentedon Aug 11, 2025
@AyanSinhaMahapatra you said you have a script to run scans, and get summaries and look for issues with --todo , feel free to let me know if I can help with anything
pombredanne commentedon Sep 3, 2025
@chinyeungli this make sense. At some point of time, creating a pipeline can work too.
AyanSinhaMahapatra commentedon Sep 3, 2025
@chinyeungli @pombredanne update on this:
I had an incomplete report, see for details:
projects_review_v1.csv
The scan was stuck because of some repos like https://github.com/jakub014/CG-dependency-analyzer which are not really great examples and have lots of manifests (at https://github.com/jakub014/CG-dependency-analyzer/tree/master/src/main/resources/poms) which cause issues and large scan times. We can remove these kind of repos from the benchmark, we should only use: popular packages with the useful type of manifests and which are packages/libraries and not data repos/other projects.
I could not finish the scans as I was looking to run the scans inside somekind of timeout using src/scancode/interrupt.py (for the package assembly step) so we are not stuck there. I still have to update the script and rerun this so we finish scanning all the packages here.
Yes, but this is to measure the times and identify performance issues in scancode-toolkit (and we're using https://github.com/aboutcode-org/scancode-toolkit/tree/package-assembly-measure which I'm not sure we can merge) so we need the script in the short term atleast. But yes we do support running pipelines with SCIO for multiple inputs using
batch-createfrom a CSV which we can enhance.Attaching the script also for reference:
fetch-scan-review.py
chinyeungli commentedon Sep 3, 2025
@AyanSinhaMahapatra let me know if there's anything that I can help here.
Add initial multiregex implementation
Improve package scan performance (#4606)
pombredanne commentedon May 14, 2026
This is partially done:
@AyanSinhaMahapatra what's left to do?
AyanSinhaMahapatra commentedon Jun 26, 2026
I added a timeout to the plugins and process codebase step with a new CLI option, see:
Restarted the benchmarking scans with this. Will do the same for scancode.io once this finishes.
AyanSinhaMahapatra commentedon Aug 4, 2026
See #4061 (comment) above for more details on the benchmarking methods.
See package scan and package assembly step execution times.
Execution script has been improved to:
We should improve the inputs to include more popular repos in addition to covering different manifests/workspaces/monorepos structures.