Better inform users about depth of search and skips in dependency scanning

NOTE if you are a user who also would like to see this feature, please UPVOTE 👍 it and comment to help it get prioritized (So it’s raised as part of our sensing mechanisms. Comments ideally should include what you want, how it would help you, what your pain point/frustration is today, and anything else that can help us focus on solving the problem.

If you are a team member commenting on behalf of a user (not ideal, as you can only upvote once!) Please remember to upvote and include as much information (what they are trying to solve for, their setup) as possible in addition to a salesforce or zendesk link.

Release notes

Problem to solve

as discussed today - when considering sub-directories - we should work to message (info) in logs better the depth of our search as well as skipped/excluded files so that users can better tell what is and is not included to help avoid a false sense of security

we also should clearly document default behavior in user docs and say where in logs to look for more info / messages

we should consider/make backlog if we don't have one already for allowing more depth/control over scan files for users to share what customizations they would like

Intended users

User experience goal

Proposal

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references