jfrog / jfrog/jfrog-cli-security
Support .slnx (XML) solution format in jf audit / NuGet & .NET project discovery
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
jf audit discovers .NET projects by parsing the solution file, but it only understands the classic .sln; with the new XML-based .slnx it finds no projects and silently scans nothing.
Describe the solution you'd like to see
Make jf audit parse .slnx the same as .sln — enumerate the referenced projects from its XML and build the dependency graph per project - treating both formats as equivalent inputs.
Describe alternatives you've considered
Keeping a parallel .sln, generating a temporary .sln in CI, or running jf audit per .csproj - all are workarounds that add maintenance/CI overhead and are easy to forget.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at jf audit’s solution-discovery and parser entry point, then compare the existing .sln handling with the .slnx XML structure. Trace how referenced projects become the per-project dependency graph, and verify that jf audit discovers the same projects from both formats; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100