Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[qa] Stress test blint by running against /usr/bin, /usr/lib etc #80

Open
prabhu opened this issue Apr 5, 2024 · 2 comments
Open

[qa] Stress test blint by running against /usr/bin, /usr/lib etc #80

prabhu opened this issue Apr 5, 2024 · 2 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@prabhu
Copy link
Member

prabhu commented Apr 5, 2024

Running it against such large directories should result in a good quality component list and dependency tree. It will help identify performance bottlenecks etc.
@prabhu prabhu added good first issue Good for newcomers help wanted Extra attention is needed labels Apr 5, 2024
@ittach1
Copy link
Contributor

ittach1 commented Apr 11, 2024

I ran the blint tool on the /usr/bin and /usr/lib directories, and it performed well! It produced JSON output files for all the binaries along with the security findings in both JSON and HTML format.

Unfortunately, the SBOM generation encountered a few failures. The process got killed automatically after some time upon execution.

@prabhu prabhu mentioned this issue May 18, 2024
Merged
@prabhu
Copy link
Member Author

prabhu commented May 28, 2024

@ittach1 how is this looking with the latest version of blint?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@prabhu @ittach1