# β About Actually when we ask to `grype` to analyze something that is not an image or a real file path it fails after having attempted all possible options : <img width="1210" height="183" alt="Image" src="https://github.com/user-attachments/assets/6b74c563-6e00-4a8b-bd4f-bb5a35ad358e" /> ...yet, sometimes the target file can be an executable in the `PATH` : <img width="745" height="400" alt="Image" src="https://github.com/user-attachments/assets/9968510c-85b4-49b4-8116-e404d151f144" /> So a simple workaround is to do as follows : <img width="745" height="299" alt="Image" src="https://github.com/user-attachments/assets/a3c2ce88-0718-42ab-ba6f-e676aa22b936" /> # π― Feature request Before exiting in error, trying to target the file/command in the `PATH` could make the UX even better : what do you thing about it ?