suspicious
afl
| suspicious | afl | |
|---|---|---|
| 5 | 6 | |
| 51 | 605 | |
| - | 0.0% | |
| 0.0 | 0.0 | |
| about 2 months ago | over 6 years ago | |
| Python | C | |
| GNU Affero General Public License v3.0 | - |
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.
suspicious
-
Catching bugs in code with AI, fully local CLI app
Here it is - https://github.com/sturdy-dev/suspicious
- Suspicious – Catching bugs in code with AI, fully local CLI app
- Show HN: Suspicious – Catching bugs in code with AI, fully local CLI app
-
AI Found a Bug in My Code
i made an open source implementation of this idea, not sure if OP did it the same way https://github.com/sturdy-dev/suspicious
afl
- American fuzzy lop: a security-oriented fuzzer
-
A convenient C string API, friendly alongside classic C strings.
You're in for a treat! I used afl, or american fuzzy lop, more specifically the afl++ fork packaged by Debian. The original usage is super simple, and many programs require little or no changes for fuzzing. The program must accept input on standard input or through a file named by a command line argument. When that's the case, compile with afl-gcc, a gcc wrapper which instruments branches, the then run the fuzzer with afl-fuzz.
-
Everything You Need to Know About Cybersecurity [91 Blog Posts]
American Fuzzy Lop (AFL) is awesome. It’s easily the best thing out there for quickly doing cutting-edge fuzzing analysis on command line applications. But what about the situations where accessing the stuff you want to fuzz via command line isn’t so simple? Lots of times you can write a test harness (or maybe use libFuzzer instead), but what if you could just emulate the parts of the code that you want to fuzz and still get all the coverage-based advantages of AFL? For example, maybe you want to fuzz a parsing function from an embedded system that receives input via RF and isn’t easily debugged. Maybe the code you’re interested in is buried deep within a complex, slow program that you can’t easily fuzz through any traditional tools.
-
Hyperpom: An Apple Silicon Fuzzer for 64-bit ARM Binaries
I dont know if it will work for riscv but I do regularly use this https://lcamtuf.coredump.cx/afl/
- AI Found a Bug in My Code
-
Ask for benchmark. The owner can’t verify a 18% perf gain, could you?
I suppose libdislocator doubles as that.
What are some alternatives?
Review Board - An extensible and friendly code review tool for projects and companies of all sizes.
STC - A modern, user friendly, generic, type-safe and fast C99 container library: String, Vector, Sorted and Unordered Map and Set, Deque, Forward List, Smart Pointers, Bitset and Random numbers.
codecat - CodeCat is an open-source tool to help you find/track user input sinks and security bugs using static code analysis. These points follow regex rules. Beta version.
snmalloc-rs - rust bindings of snmalloc
Auto-GPT - An experimental open-source attempt to make GPT-4 fully autonomous. [Moved to: https://github.com/Significant-Gravitas/AutoGPT]
flamegraph - Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3
dom - DOM Standard
diffctx - A GitHub action for automatically evaluating the logic level impacts of Pull Requests. Multi languages support.
str - C String handling library inspired by Luca Sas
sbs - A reformulation of sds (https://github.com/antirez/sds) for buffers
rapidyaml - Rapid YAML - a library to parse and emit YAML, and do it fast.