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
What happened: Running syft 0.71.0 on docker.io/python:3.8.16-slim-bullseye shows two python binaries detected using metadata, but there is only one python package installed in the image.
What you expected to happen:
I expect the output to have a single "python" package binary detected using either or both of the pieces of evidence from the 'python-binary-lib' and 'cpython-source' classifiers if they are operating on the same package's metadata.
The above is just an example of something that would make sense, not exactly what I expect to see or even be possible.
I'm not sure how to make it clear which evidence (the lib or the cpython .h stuff) was used to determine the package, but the general approach I think could be to use those classifiers to determine the version of the python binary. I'm not sure how the paths could/should line up, but I think its better to be more narrowly constrained and correct than to report multiple entries.
Steps to reproduce the issue: syft docker.io/python:3.8.16-slim-bullseye -o json=sbom.json
What happened: Running syft 0.71.0 on docker.io/python:3.8.16-slim-bullseye shows two python binaries detected using metadata, but there is only one python package installed in the image.
Excerpt of the output:
However, looking in the image I see only one install of python:
What you expected to happen:
I expect the output to have a single "python" package binary detected using either or both of the pieces of evidence from the 'python-binary-lib' and 'cpython-source' classifiers if they are operating on the same package's metadata.
Something like:
The above is just an example of something that would make sense, not exactly what I expect to see or even be possible.
I'm not sure how to make it clear which evidence (the lib or the cpython .h stuff) was used to determine the package, but the general approach I think could be to use those classifiers to determine the version of the python binary. I'm not sure how the paths could/should line up, but I think its better to be more narrowly constrained and correct than to report multiple entries.
Steps to reproduce the issue:
syft docker.io/python:3.8.16-slim-bullseye -o json=sbom.json
Anything else we need to know?:
Environment:
syft version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: