-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add security checks #1385
Add security checks #1385
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1385 +/- ##
==========================================
+ Coverage 96.19% 96.29% +0.10%
==========================================
Files 86 89 +3
Lines 7301 7476 +175
==========================================
+ Hits 7023 7199 +176
+ Misses 278 277 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good.
Bandit has found a few assert statements in non-test code. I'll create another issue to tackle those.
Thank you @dmentipl! Looks good. I'm half wondering if bandit should just fail - what do you think? |
No worries, @benfitzpatrick! We certainly could fail with bandit. However, it does pick up things like using assert, which is a low severity issue. We could add the What do you and @tjtg think? |
We should make it so that bandit fails if it identifies issues, but not right now. |
* Add safety and bandit to tests * Add name to CONTRIBUTING.md
Addresses #1382
Run bandit and safety as part of CI. Bandit finds common security issues in Python code. Safety checks installed dependencies for know security vulnerabilities.
If bandit/safety find any issues the tests will not fail. However, the output is written to the log (in GitHub Actions) for inspection.
Testing:
CLA