-
Notifications
You must be signed in to change notification settings - Fork 136
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 Yarn #367
Comments
Hi @quinnturner, |
one lazy sidestep is to use https://github.com/imsnif/synp to work with yarn.lock file |
Attached is a simple project (hubot, generated using https://github.com/HelloRusk/generator-hubot-yarn) that has a yarn.lock file. The aforementioned project also has a yarn.lock file available for review: https://github.com/HelloRusk/generator-hubot-yarn/blob/master/yarn.lock) |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
Is there any update on this ? Or any known workaround ? |
hello, any update regarding this? |
Encountered the same issue. Up |
Same with php's composer.lock (experimental). |
IMHO this plugin should provide a way to force sonar to follow all untracked files returns by depency-check analysis, a failsafe dummy language ? |
With the release of
Dependency-Check
v6.1.0 (and subsequent fixes in v6.1.1), Yarn auditing is supported natively.In this plugin, the logs that I receive during my CI pipeline suggest that Yarn is not directly supported.
Where the project's
sonar-project.properties
contains the value:Describe the solution you'd like
This plugin should support Yarn now that
Dependency-Check
supports auditing withyarn audit --verbose
with the fileyarn.lock
.The text was updated successfully, but these errors were encountered: