-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support for polyglot monorepos? #69
Comments
@davidkeaveny This issue might be a better one to take to the upstream microsoft/component-detection repository? I'm not sure why it's failing to detect your .NET projects, but they should be able to say more. cc: @JamieMagee |
I updated to v0.0.3, and tweaked my workflow as follows: name: sbom
on:
pull_request:
types: [opened, synchronize, reopened]
branches:
- main
jobs:
dependency-submission:
name: Analysing dependencies
runs-on: ubuntu-latest
steps:
- name: Checkout source
uses: actions/checkout@v4
- name: Detect components
uses: advanced-security/[email protected]
with:
directoryExclusionList: "**/tests/**,**/docs/**,**/devops/**"
detectorsFilter: "NpmWithRoots,NuGet" And this gives me the expected results:
(snipping out unimportant entries). So I don't know if it's adding the explicit |
I have a repository that contains a mix of ReactJS and .NET Core applications (which use central package management, with a
Directory.Packages.props
file in the root folder). When I run the v0.0.2 tool against the repo, it reports on the NPM packages referenced frompackage.json
, but doesn't report on any .NET packages.My GitHub workflow is:
It will then produce an output like this:
I've tried setting
filePath
to a folder which contains only a .NET project, but it makes no difference, the project isn't scanned and no NuGet packages are reported.The text was updated successfully, but these errors were encountered: