
Scan code for origin, license and vulnerabilities
Showing 5 of 26 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Sampurna Pyne(Samk)
Currently, VulnerableCode lacks built-in insights to demonstrate its effectiveness. This project addresses this by integrating a telemetry dashboard into the Web UI to visualize reliability, growth, and data quality.
Mentors: Student: Kaushik Kumar
ScanCode-Toolkit relies on "required phrases" to prevent false positive license detections, but 74% of its rules currently lack this protection. To solve this, I am building an AI/NLP pipeline that automatically reads raw license texts and extracts the exact phrases needed to protect these rules. I have already built a working proof-of-concept, complete with a trained model and a live web demo that the maintainers can test right now. During GSoC, I will build this into a lightweight, production ready tool. My core deliverables include a highly accurate machine learning model optimized for offline use and a native Command Line Interface (CLI). This tool will automatically inject high-confidence phrases and provide an interactive "human-in-the-loop" review mode for edge cases, ultimately delivering a measurable reduction in real world false positives.
Mentors: Student: AayushKumar
The current directory browsing experience in ScanCode.io is limited to viewing one folder at a time, which becomes inefficient and cumbersome for navigating large codebases. This project aims to enhance the usability of ScanCode.io by implementing a file-system tree view that provides a more structured and user-friendly navigation experience.
Mentors: Student: Alokkumar97
This project focuses on improving the accuracy and clarity of the detection_log by explicitly identifying when extra-words are detected during license rule matching. These extra-words often represent variable components within license texts, which previously caused the match score to drop below 100 even when the overall match was correct. To resolve this issue, the implementation now checks whether the extra words appear in the expected position within the license text. If their position is valid, the match score is adjusted to 100, and it is also reflected in detection_log. This enhancement leads to more precise license rule matching and provides users with clearer, more reliable detection results.
Mentors: Student: Michael Ehab Mikhail
Currently, VulnerableCode runs importers in bulk where all the data from advisories are imported (and reimported) at once and stored to be displayed and queried. The objective of this project is to have another endpoint and API where we can dynamically import available advisories for a single PURL at a time. This API will be used to improve VulnTotal by supporting a local mode for the VulnerableCode data source. Additionally, this update will benefit the VulnTotal browser extension, which will be updated as well and will ensure direct and easy interaction with the new VulnerableCode API endpoint.