refactor
semgrep
Our great sponsors
refactor | semgrep | |
---|---|---|
7 | 74 | |
434 | 9,724 | |
- | 2.5% | |
0.0 | 9.9 | |
4 months ago | 3 days ago | |
Python | OCaml | |
MIT License | GNU Lesser General Public License v3.0 only |
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.
refactor
- Refactor: Python Refactoring tool at the AST level
- GitHub - isidentical/refactor: Simple python source refactoring toolkit based on AST
-
Show HN: Python Source Code Refactoring Toolkit via AST
Indeed! I also would suggest people to use a CST implementation (parso / LibCST) instead of refactor if they intend do large scale refactors, but from what I can see in my previous attempts (e.g teyit, a unittest assertion formatter) when you deal with small code fragments (a single expression, or a small statement) then you generally don't need to worry much about the style. The only concern is the literals (especially strings, which there are a few different variations of the same AST) where you could resurrect them back from the token stream (which the CustomUnparser representative in refactor allows).
The real start point for this project was to find / replace all type()'s in CPython codebase with type(type()) (e.g type('') would become type(str)) which is very light weight transformation, and I was able to write a script which did it without having any major problems about style on over 2000 files. Here it is for the reference: https://github.com/isidentical/refactor/blob/master/examples...
Also one thing to note here is that; in the last couple of years, thanks to black (and yapf), the adoptance of code formatters have really increased which is very nice for custom refactoring tools like refactor since the end-code would be refactored anyways so that means if you convert a multi line call, or a list to a single line version then the formatter you use probably reformat that segment anyways.
But thanks for authoring Bowler! It is a very cool project.
- Simple python source refactoring toolkit based on AST
-
refactor: AST based source code refactoring for Python
I've just released 0.2.0 version of refactor, https://github.com/isidentical/refactor, which features additional information collection from the surrounding code.
- AST based source refactoring toolkit
semgrep
-
A Deep Dive Into Terraform Static Code Analysis Tools: Features and Comparisons
Semgrep OSS Owner/Maintainer: Semgrep Age: First release on GitHub on February 6th, 2020 License: GNU Lesser General Public License v2.1
- Semgrep – Find bugs and enforce code standards
-
Application Security - Bridging Frontend and Cybersecurity: What is Application Security?
Semgrep - https://semgrep.dev
-
Creating a DevSecOps pipeline with Jenkins — Part 1
For the SAST stage, I used SonarQube tool. SonarQube is an open-source platform developed by SonarSource for continuous inspection of code quality to perform automatic reviews with static analysis of code to detect bugs and code smells on more than 30 programming languages. I preferred SonarQube instead of other SAST tools because it has a detailed documentation and plugins about integration with Jenkins and SonarQube works with Java projects pretty well. Of course you can similar multi-language-supported tools such as Semgrep or language-specific tools such as Bandit.
-
Tree-Sitter
> Not sure I understand your point.
The problem is using Treesitter (for syntax highlighting and "semantic movements") and an LSP at the same time. So if your language has a LSP, using Treesitter additionally is redundant at best and introduces inconcistency at worst.
I'm not talking about using Treesitter as the parser for the LSP.
> Most popular languages have language-specific tools
I'd say even less popular langauges like Coq^H^H^HRocq, Lean 4, Koka, Idris, Unison, ... have their "own" tools, I do not know of a language that uses a Treesitter parser in its LSP, but I do know about tools like https://semgrep.dev/ (written in OCaml) and Github's code search which use Treesitter.
-
AST-grep(sg) is a CLI tool for code structural search, lint, and rewriting
Well, when I seach for "semgrep", I get a very nice corporate landing page with a "Book Demo" button. Which is a level of hassle that just isn't worth it for smaller teams, because "Book Demo" usually means "We're going to try to do a dance to see how much money we can extract from you." Which smaller teams may only want to do for a handful of key tools.
(4 years ago, I was more willing to put up with enterprise licensing. But in the last two years, I've seen way too many enterprise vendors try to squeeze every penny they can get from existing clients. An enterprise sales process now often means "Expect 30% annual price hikes once you're in too deep to back out.")
There's also an open source "semgrep" project here: https://github.com/semgrep/semgrep. But this seems to be basically a vulernability scanner, going by the README.
Whereas AST-grep seems to focus heavily on things like:
1. One-off searching: "Search my tree for this pattern."
2. Refactoring: "Replace this pattern with this other pattern."
AST-grep also includes a vulnerability scanning mode like semgrep.
It's possible that semgrep also has nice support for (1) and (2), but it isn't clearly visible on their corporate landing page or the first open source README I found.
-
Top 10 Snyk Alternatives for Code Security
7. Semgrep
- Semgrep: Semantic Grep for Code
-
semgrep VS bearer - a user suggested alternative
2 projects | 10 Jul 2023
-
Powerful SAST project for Android Application Security
This project is a compilation of Semgrep rules derived from the OWASP Mobile Application Security Testing Guide (MASTG) specifically for Android applications. The aim is to enhance and support Mobile Application Penetration Testing (MAPT) activities conducted by the ethical hacker community. The primary objective of these rules is to address the static tests outlined in the OWASP MASTG.
What are some alternatives?
Bowler - Safe code refactoring for modern Python.
SonarQube - Continuous Inspection
py2js
snyk - Snyk CLI scans and monitors your projects for security vulnerabilities. [Moved to: https://github.com/snyk/cli]
hpy - HPy: a better API for Python
codeql - CodeQL: the libraries and queries that power security researchers around the world, as well as code scanning in GitHub Advanced Security
prefactor - Tool for writing Python refactorings
Spotbugs - SpotBugs is FindBugs' successor. A tool for static analysis to look for bugs in Java code.
Rope - a python refactoring library
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
detect-secrets - An enterprise friendly way of detecting and preventing secrets in code.
gitleaks - Protect and discover secrets using Gitleaks 🔑