Replies: 2 comments 4 replies
-
@SF97, thank you for the kind words. Wondering if we can run from the root of the repository and then filter based on component.properties. Is there anything useful in those attributes? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I don't think there's anything useful there for this use case. It's mostly objects with name property set to |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello
First and foremost, thank you for this project :) We need to build SBOMs for compliance and vulnerability scanning, and it is great!
Now to my question :)
We run a large monorepo in my company. This monorepo has two products in it. It has microservices that are mostly in JavaScript with dependencies managed by pnpm. Some microservices belong to one product only, and some are shared between both products. The structure is similar to this:
Each service depends on libs that are in different folders.
Ideally, we would like to get an SBOM for each service in the repository, but an SBOM per product should also work. I've been trying to get an SBOM for each service with this tool, but I haven't had any success so far. When running the tool inside each service, the SBOM information only contains info about the tool:
I guess this is due to the
pnpm-lock
file being at the top of the repository.If I run the tool at the top of the repository, information about dependencies is shown. However, the information accounts for both products, and I need to have information per-product
Is there a way to get an SBOM for a single service in the monorepo, no matter where it is located?
Beta Was this translation helpful? Give feedback.
All reactions