You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within the LFX Security service, Snyk is attempting to scan security risks in this repo.
Snyk uses the pattern **/*req*.txt to find requirements files, and it can't seem to be coerced to try anything else.
I guess if we rename our dependency files from (for example) app.txt to app-requirements.txt, then Snyk finds them after all.
We don't need a Snyk account for LFX Security, but we could try out locally with the Snyl CLI if the naming is actually the culprit (and if renaming solves it). For that, we probably should make an account.
We might need to follow up with the renaming in a couple of other places, of course, like the Dockerfile or other CI-related things.
The text was updated successfully, but these errors were encountered:
Within the LFX Security service, Snyk is attempting to scan security risks in this repo.
Snyk uses the pattern
**/*req*.txt
to find requirements files, and it can't seem to be coerced to try anything else.I guess if we rename our dependency files from (for example) app.txt to app-requirements.txt, then Snyk finds them after all.
We don't need a Snyk account for LFX Security, but we could try out locally with the Snyl CLI if the naming is actually the culprit (and if renaming solves it). For that, we probably should make an account.
We might need to follow up with the renaming in a couple of other places, of course, like the Dockerfile or other CI-related things.
The text was updated successfully, but these errors were encountered: