Brakeman
Pundit
Our great sponsors
Brakeman | Pundit | |
---|---|---|
16 | 25 | |
6,906 | 8,164 | |
- | 0.6% | |
8.1 | 6.9 | |
2 days ago | 22 days ago | |
Ruby | Ruby | |
Q Public License 1.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Brakeman
-
First commits in a Ruby on Rails app
Brakeman - “Brakeman detects security vulnerabilities in Ruby on Rails applications via static analysis”
-
[Tool] An alternative to Brakeman for Security
My team and I released Bearer a couple of weeks ago, a newer open and free alternative to Brakeman to check your code for security and privacy risks. In addition to Ruby/Rails, we also cover your JS/TS code, which allows you to use a single solution for your whole Rails application.
-
Brakeman VS bearer - a user suggested alternative
2 projects | 10 Jul 2023
-
Code Reviewing a Ruby on Rails application.
Brakeman is a static analysis security vulnerability scanner for Ruby on Rails applications. It finds potential security issues in Rails applications by examining the Ruby code. Brakeman helps find and fix security holes before deploying your Rails app.
-
4 Essential Security Tools To Level Up Your Rails Security
brakeman is another useful Ruby gem that is a static analysis security vulnerability scanner for Ruby on Rails applications.
-
How do you guys integrate automated security checks in your CI/CD pipelines?
You might find brakeman interesting: https://brakemanscanner.org
-
Github Pre-commit Hook Setup In Ruby On Rails for maintaining coding standards and productive.
It’s assumed that you already have a Rails app and use Brakeman to keep your app secure and Rspec to run your test cases.
- Is this query vulnerable to SQL injections?
-
Security Risks On Rails: Misconfiguration and Unsafe Integrations
Another great lib for this is Brakeman, which can be installed in a very similar process and gives you even more detailed reports:
-
Fixing Just One False Positive in Brakeman
This is pretty easy to handle. In the case where a splatted array is the only argument to a method, we'll simply use the elements of the array as the argument list. (Check out the pull request here)
Pundit
-
A guide to Auth & Access Control in web apps 🔐
https://github.com/varvet/pundit Popular open-source Ruby library focused around the notion of policies, giving you the freedom to implement your own approach based on that.
-
Pundit VS Action Policy - a user suggested alternative
2 projects | 2 Jul 2023
-
Launch HN: Infield (YC W20) – Safer, faster dependency upgrades
Can you expand a little? Here's some technical background on what we're doing:
We have our own database of every version of every rubygems package alongside its runtime dependencies (like you see at https://rubygems.org/gems/pundit).
Then we parse your Gemfile and Gemfile.lock. We use the Gemfile to figure out gem group and pinned requirements (we run turn your Gemfile into a ruby AST since Gemfiles can be arbitrary ruby code; we use bundler's APIs to parse your Gemfile.lock). This gives us all of the dependencies your rely on.
Then we let you choose one or more package that you want to upgrade and the version you want to target (let's say Rails 7.0.4.3).
Now we have [your dependencies and their current versions], [target rails version], [all of the runtime dependency constraints of these gems]. We run this through a dependency resolution algorithm (pubgrub). If it resolves then you're good to upgrade to that version of Rails without changing anything.
If this fails to resolve, it's because one or more of your current dependencies has a runtime restriction on rails (or another indirect gem being pulled in by the new rails version). This is where the optimization part comes in. The problem becomes "what is the optimal set of versions of all your dependencies that would resolve with the next version of Rails". Currently we solve for this set trying to optimize for the fewest upgrades. As our dataset of breaking changes gets better we'll change that to optimizing for the "lowest effort".
Happy to elaborate.
-
Authentication, Roles, and Authorization... oh my.
For authorization, I'm going back and forth with Pundit and CanCanCan
-
Protect your GraphQL data with resource_policy
Expressing authorization rules can be a bit challenging with the use of other authorization gems, such as pundit or cancancan. The resource_policy gem provides a more concise and expressive policy definition that uses a simple block-based syntax that makes it easy to understand and write authorization rules for each attribute.
-
Default to Deny for More Secure Apps
As an example of how to default to deny, consider a Ruby on Rails app (as we tend to do). The primary way a user interacts with the app is through API endpoints powered by controllers. We use Pundit, a popular authorization library for Rails, to manage user permissions.
-
Permissions (access control) in web apps
https://github.com/varvet/pundit Popular open-source Ruby library focused around the notion of policies, giving you the freedom to implement your own approach based on that.
-
YAGNI exceptions
PS If you do mobile / web work (or something else with "detached" UI), I find that declarative access control rules are far superior to imperative ones, because they can be serialized and shipped over the wire. For example, backend running cancancan can be easily send the same rules to casl on the frontend, while if you used something like pundit to secure your backend, you either end up re-implementing it in the frontend, or sending ton of "canEdit" flags with every record.
-
Best practice for displaying info to different user roles?
You can use a combination of an authorization gem (https://github.com/varvet/pundit) and decorators (https://www.rubyguides.com/2018/04/decorator-pattern-in-ruby/) if you want to extend functionality based on their roles.
-
Concerns about authorization when going in production
Use Action Policy or Pundit, and write tests for your policies. Authz is worth testing with near complete coverage.
What are some alternatives?
bundler-audit - Patch-level verification for Bundler
CanCanCan - The authorization Gem for Ruby on Rails.
Rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide. [Moved to: https://github.com/rubocop/rubocop]
rolify - Role management library with resource scoping
Metasploit - Metasploit Framework
Action Policy - Authorization framework for Ruby/Rails applications
Rubycritic - A Ruby code quality reporter
Devise - Flexible authentication solution for Rails with Warden.
Pronto - Quick automated code review of your changes
Authority
BeEF - The Browser Exploitation Framework Project
Declarative Authorization - An unmaintained authorization plugin for Rails. Please fork to support current versions of Rails