Skip to content

feat: OutputEngine updates for no-scan #5195

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

Merged
merged 8 commits into from
Jul 27, 2025

Conversation

joydeep049
Copy link
Contributor

OutputEngine Updates for No-Scan Work.
Currently the console throws a bunch of vendor, product, version and last stable version information as a table output

@joydeep049
Copy link
Contributor Author

=========================== short test summary info ============================
FAILED test/test_output_engine.py::TestOutputEngine::test_output_with_unset_fields - AssertionError: OutputEngine.output_cves raised an exception when 'sbom_serial_number' was unset: cannot unpack non-iterable NoneType object
FAILED test/test_source_purl2cpe.py::TestSourceOSV::test_db_contents[1-False] - AssertionError: Missing elements in database: ['pkg:1234n/minicms', 'pkg:13thmonkey/udfclient', 'pkg:23systems/lightbox-plus-for-wordpress', 'pkg:2glux/sexypolling', 'pkg:2pisoftware/cmfive']
assert not ['pkg:1234n/minicms', 'pkg:13thmonkey/udfclient', 'pkg:23systems/lightbox-plus-for-wordpress', 'pkg:2glux/sexypolling', 'pkg:2pisoftware/cmfive']
=========== 2 failed, 297 passed, 2035 skipped in 167.64s (0:02:47) ============

Both of these failing tests are unrelated to my changes. The OSV one is pretty expected since @terriko mentioned that there might be some missing data. The other one one seems to be a problem with lib4vex, so tagging @anthonyharrison here

@mastersans mastersans self-requested a review July 25, 2025 17:27
@anthonyharrison anthonyharrison merged commit b6a1e5e into intel:main Jul 27, 2025
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants