cml_dvc_case VS leaky-repo

Compare cml_dvc_case vs leaky-repo and see what are their differences.

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
cml_dvc_case leaky-repo
1 2
18 211
- -
0.0 0.0
6 months ago about 1 year ago
Python Python
- 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.

cml_dvc_case

Posts with mentions or reviews of cml_dvc_case. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-12-08.

leaky-repo

Posts with mentions or reviews of leaky-repo. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-08.
  • Nosey Parker: a new scanner to find misplaced secrets in textual data and Git history
    4 projects | /r/netsec | 8 Dec 2022
    Also, I've built a repo of credentials and benchmarked several tools including trufflehog against it if you want to see how your tool and default ruleset stack up: https://github.com/Plazmaz/leaky-repo
  • Discover Hidden Secrets in Git Repos with Rust
    3 projects | dev.to | 8 Nov 2021
    At this point, we've succeeded at what we set out to create. I went ahead and scanned common testing repositories for this sort of thing like Plazmaz/leaky-repo and dijininja/leakyrepo. In general the program found all or most of the secrets. In the case of dijininja/leakyrepo it found a lot of RSA private keys which is acceptable but technically a misidentification. For Plazmaz/leaky-repo we find the majority of the keys although once again misidentify some. The decision to use rust makes performance really solid although still a little slow even for small repos. A couple good extensions to this to help with that could be adding a thread pool in order to scan objects in parallel. In more professional code, it seems more idiomatic for the scan_objects() function to return some objects of objects including their results rather than just printing the one containing secrets. For example, it could be formatted something like this:

What are some alternatives?

When comparing cml_dvc_case and leaky-repo you can also consider the following projects:

example-get-started - Get started DVC project

leakyrepo - A repo which contains lots of things which it shouldn't