Git Hub Advanced Scanning - dependency scanning - libman.json #120191
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
We have enabled advanced security in our Azure dev ops setup and we've noticed for our .net core application, the dependency scanner is not detecting any client side libraries, even though we know we have issues.
Looking into the requirements i suspect this is because we use libman.json to define out client side libraries, built into VS, which isn't supported, when reviewing the documentation as far as i can tell.
So i guess we may have to use npm package manager or something for the scanning to determine our client side libraries, given I'm presuming it doesn't just scan the folders to work this out?
Beta Was this translation helpful? Give feedback.
All reactions