-
Notifications
You must be signed in to change notification settings - Fork 4
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
Enable Dependabot for NPM packages #86
Comments
@btlogy may be you could look at this issue? |
I just had a quick look. And my first impressions are:
@wuan, can you give us some guidance on how to go further here? As for the discussion, I'm not sure there is a way to scan only production packages. In a repository I'm testing, it seems like we can only enable or disable the Dependabot Alert feature. Not much to configure there. |
I was more thinking about security alerts. There are possibility to configure via Github interface, but maybe it is possible to configure via .yml file: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file and then push changes here? |
Also now, if we run npm audit, it will find some issues, but if we omit=dev packages, currently there is no vulnerabilities (by npm audit). For discussion, should we enable for all packages and have pain or should we focus only for prod packages usage (which are deployed)? |
Support for the It would be best to set this via the Terraform configuration. |
Good catch @wuan. My search results were empty there (not always indexed apparently). |
This looks like a nice way to tune Dendendabot @donpui, but I think it needs to be enabled for the repository first. |
With this in mind, and since it is only about alerting: should we not then add a GitHub action to I'm only asking because enabling this as requested would mean using yet another platform feature we can rely on only for some of our projects (i.e.: not for PrivateStorageWeb for instance). |
We can have a mix usage, run in Github Actions and also on Github. Github Dependabot provide some Web interface and also can create PRs. |
Lets enable Dependabot first (as it is quickest open), while we explore and make other more common via all repos approach. |
Actually dependabot is already enabled in this repo, however only Admin level can see. Plus or not, if security check runs in CI, it could be seen for lower rights users. |
Nearly 2 months since mineiros-io/terraform-github-repository#143 and not yet merged... |
We can enable Dependabot manually for selected repositories so that we do not need to wait for the update and in parallel all click on the thumbs up here: mineiros-io/terraform-github-repository#145. |
Winden it is already enabled. |
For the record: I've tested |
Having a look at the "Code security and analysis" section in the repo settings it looks like Dependabot is enabled: |
Thank you @wuan. From this screenshot we can confirm Dependabot is enabled, but altering is disabled!
@donpui replied:
Thus, is this issue really resolved? |
Alerts are enabled, button shows, that you can disable :) However, they are visible in Security Dashboard, but only who have certain rights. Dependabot also allows to create PR automatically, however, this means public disclosure. |
Oups... |
Enable Github Dependabot for NPM packages to scan for security issues with packages.
For discussion, should we configure only production packages scanning or also devDependencies?
The text was updated successfully, but these errors were encountered: