spdk
find-sec-bugs
Our great sponsors
spdk | find-sec-bugs | |
---|---|---|
6 | 8 | |
2,829 | 2,204 | |
2.3% | 1.2% | |
9.9 | 6.1 | |
4 days ago | about 2 months ago | |
C | Java | |
GNU General Public License v3.0 or later | 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.
spdk
-
calcuating IOPS
https://spdk.io will require you to load linux onto the server (livecd off a usb should be fine), but is essentially the most efficient way possible to do IO. Intel’s storage division used to use it to get the numbers they advertised with. When they loaded up a system with kioxia drives, Intel managed to hit 120 million IOPS in some of their testing.
- Storage performance development kit
- Win32 is the stable Linux userland ABI
- SPDK: Storage Performance Development Kit
-
ShellCheck: A static analysis tool for shell scripts
Since the project I work on (https://spdk.io) largely produces a set of executables as output, it was most natural to write the tests in bash. There's one top level bash script that kicks off the full suite of tests and thousands and thousands of lines of tests all written as bash scripts stringing together calls to these executables.
One of these tests is to run shellcheck against all of the scripts in the repo. We don't allow any modifications to scripts without shellcheck giving them the green light now. The quality of our tests has increased dramatically since this was instituted - it's a really great tool.
-
Achieving 11M IOPS and 66 GB/S IO on a Single ThreadRipper Workstation
FYI SPDK doesn't strictly require the IOMMU be enabled. See https://spdk.io/doc/system_configuration.html There's also a new experimental interrupt mode (not for everything) finding some valuable use cases in SPDK, see https://github.com/spdk/spdk/blob/master/CHANGELOG.md and feel free to jump on the SPDK slack channel or email list for more info on either of these https://spdk.io/community/
find-sec-bugs
- Find Security Bugs
-
What are some useful static analyzers for Java?
SpotBugs have a lot of extensions such as https://find-sec-bugs.github.io/ https://github.com/KengoTODA/findbugs-slf4j and more, I recommend adding them as well
-
Looking for a Static Code Analysis tool for Scala Code
If you don’t have checkmarx/Vera code money, have you looked at https://find-sec-bugs.github.io/? It can be used with a few things such as https://spotbugs.github.io/ and sonarQ
-
Enforcing Coding Best Practices using CI
SpotBugs with Find sec bugs for Java
-
Conducting SAST for Java Applications
How can the article fail to mention Find Security Bugs (find-sec-bugs) when talking about using SpotBugs (ex-FindBugs) for analyzing code for security issues?
-
Design an Effective Build Stage for Continuous Integration
Find Security Bugs uses a security database to detect almost 140 different vulnerability types in Java web applications.
-
ShellCheck: A static analysis tool for shell scripts
find-sec-bugs does that. It's used by, for example, SonarQube.
See hhttps://github.com/find-sec-bugs/find-sec-bugs/blob/master/f... and do a "CTRL-F" and search for "References".
What are some alternatives?
KVell - KVell: the Design and Implementation of a Fast Persistent Key-Value Store
Spotbugs - SpotBugs is FindBugs' successor. A tool for static analysis to look for bugs in Java code.
shellharden - The corrective bash syntax highlighter
semgrep-rules - Semgrep rules registry
chia-blockchain - Chia blockchain python implementation (full node, farmer, harvester, timelord, and wallet)
snyk - Snyk CLI scans and monitors your projects for security vulnerabilities. [Moved to: https://github.com/snyk/cli]
static-analysis - ⚙️ A curated list of static analysis (SAST) tools and linters for all programming languages, config files, build tools, and more. The focus is on tools which improve code quality.
semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
hadolint - Dockerfile linter, validate inline bash, written in Haskell
shunit2 - shUnit2 is a xUnit based unit test framework for Bourne based shell scripts.
infer - A static analyzer for Java, C, C++, and Objective-C