todo_or_die
Write TODOs in code that ensure you actually do them (by searls)
Our great sponsors
| bad_actor_poc | todo_or_die | |
|---|---|---|
| 12 | 3 | |
| 322 | 332 | |
| - | - | |
| 0.0 | 4.6 | |
| almost 3 years ago | 6 months ago | |
| Rust | Ruby | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
bad_actor_poc
Posts with mentions or reviews of bad_actor_poc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-06.
-
Why is `const fn` different from other “const” things?
I'm not suggesting people in this thread are wrong, but working for a security company gives a slightly different perspective. For example, there's really nothing stopping a rogue crate from exporting your private keys, just by using VS code. I wasn't thinking about this when I helped write that proposal, though.
- Did somebody play around with macros yet?
-
todo-or-die!
Having less tools that can do things like https://github.com/lucky/bad_actor_poc is a relief.
-
Workspace Trust in VS Code
Code execution that may not be so obvious could be the preLaunchTask that runs before starting the app and can run a build that has an extra task executing arbitrary code unrelated to the build. What about the npm module that steals your crypto wallet private keys? Make a simple edit and a malicious linter is loaded from the node_modules folder, instead of the one that is installed globally. Even reading the code can be deceptive, attackers can use Unicode hacks to hide malicious code in plain sight. Heck, you don't even have to open any source code to be owned.
- lucky/bad_actor_poc - Stealing secrets with Rust Macros proof-of-concept via VSCode: This shows a trivial example of exfiltrating secrets just by the developer opening up the source
- Visual Studio Code May 2021
-
Carnet: A Tool for Sandboxing Cargo and Buildscripts
https://github.com/lucky/bad_actor_poc is one example
-
Fixated on end-user security, FOSS developers neglect their own...
It turns out that because Rust can execute code at compile time, simply opening a Rust source file in an editor with code completion support can cause a virus to be installed on my computer. Apparently I can't trust anything but basic text editors anymore...
- Using Rust Macros to exfiltrate secrets
todo_or_die
Posts with mentions or reviews of todo_or_die.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-12.
-
Gem for reminding us to revisit some parts of code
But you may like https://github.com/searls/todo_or_die also
-
todo-or-die!
Seems to be "inspired" by https://github.com/searls/todo_or_die, shame that they didn't feel the need to acknowledge that in the README or elsewhere.
- todo-or-die – TODOs you cannot forget!
What are some alternatives?
When comparing bad_actor_poc and todo_or_die you can also consider the following projects:
language - Design of the Dart language
carnet - A Tool for Sandboxing Cargo and Buildscripts
code-it-later-rs - Filter crumbs you left in comments of code to remind where you were
Visual Studio Code - Visual Studio Code
sane_patch - Making monkey patches sane again
macro_prototype - A very basic prototype of macros using build_runner
tax - CLI Task List Manager
smart_todo - Enhance TODO comment in your Ruby code
security - Embargoed security issues that will be made public after a fix is made available. Use https://github.com/nim-lang/security/security
toodles - Project management directly from the TODOs in your codebase
bad_actor_poc vs language
todo_or_die vs carnet
bad_actor_poc vs carnet
todo_or_die vs code-it-later-rs
bad_actor_poc vs Visual Studio Code
todo_or_die vs sane_patch
bad_actor_poc vs macro_prototype
todo_or_die vs tax
bad_actor_poc vs code-it-later-rs
todo_or_die vs smart_todo
bad_actor_poc vs security
todo_or_die vs toodles