colors.js
cargo-crev
Our great sponsors
colors.js | cargo-crev | |
---|---|---|
52 | 55 | |
5,153 | 2,030 | |
- | 2.2% | |
0.0 | 7.9 | |
11 months ago | 23 days ago | |
JavaScript | Rust | |
GNU General Public License v3.0 or later | Apache License 2.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.
colors.js
-
Mitigate the hidden security risks of open source software libraries
However, it's unlikely that the majority of users actually visit GitHub at https://github.com/Marak/colors.js to review the code, even at a high level. Most developers tend to rely on the assurance that open source software is generally safe to use.
- when u finally found that ONE repo which fits your needs and is not outdated but you have issues to raise
-
Marak: The reports of my death have been greatly exaggerated
> A new feature was added to the colors.js project for generating cool ASCII Art American Flags. Unfortunately, this feature was not bug-free and some test code slipped into the release causing issues downstream. Nobody is perfect. Everyone makes mistakes from time to time.
https://github.com/Marak/colors.js/commits/master shows 4 commits and 2 releases. Does not seem like a simple mistake
> As per our internal open-source development process, I opened an Issue in colors to track the bug as soon as it was confirmed. It happened to be a weekend [...] I tagged some other open-source developers I've worked with in the past to see if they had time to assist and closed the browser tab.
- Recognize that there are many reasons that people create open source work...its a form of their self expression like Michelangelo or Salvador Dali, and nobody should complain if a metaphoric Jackson Pollock, decides to make their work resemble paint splatter instead of an architectural masterpiece.
- this thread will forever be living proof that the entire node ecosystem is a fucking dumpster fire.
- CVE-2021-23567
-
JavaScript News and Updates of January 2022
Early this month, the malicious attack on free-to-use libraries, namely color.js and faker.js, created a real uproar in the development community. These tools are used in thousands of projects and their downloading rate from npm is estimated in millions per week. To everyone’s surprise, it turned out to be an inside job. Marak Squires, the creator of these libraries, intentionally committed malicious code to his projects and published updated codebases on GitHub and npm. It is said that this sabotage was caused by unsuccessful attempts of Mr. Squires to monetize his projects. Fortunately, malicious packages were quickly removed and the attacker’s account was suspended. The story sparked a new wave of discussion in the development community on possible steps to make the development and maintenance of open-source projects more sustainable.
-
colors.js VS ansis - a user suggested alternative
2 projects | 24 Jan 2022
-
Marak, the guy behind the recent breaking of faker.js, colors.js, etc., claims that it was a "programming mistake" and wants Github to unban him.
See: https://github.com/Marak/colors.js/issues/285
-
Colors.js in dart.
Ever used colors.js? How about the same in dart?
cargo-crev
-
Hard disk LEDs and noisy machines
In other cases it may be more documented, such as Golangs baked-in telemetry.
There should be better ways to check these problems. The best I have found so far is Crev https://github.com/crev-dev/crev/. It's most used implementation is Cargo-crev https://github.com/crev-dev/cargo-crev, but hopefully it will become more required to use these types of tools. Certainty and metrics about how many eyes have been on a particular script, and what expertise they have would be a huge win for software.
-
Rust Without Crates.io
The main problem the author is talking about is actually about version updates, which in Maven as well as crates.io is up to each lib's author, and is not curated in any way.
There's no technical solution to that, really. Do you think Nexus Firewall can pick up every exploit, or even most? How confident of that are you, and what data do you have to back that up? I don't have any myself, but would not be surprised at all if "hackers" can easily work around their scanning.
However, I don't have a better approach than using scanning tools like Nexus, or as the author proposes, use a curated library repository like Debian is doing (which hopefully gets enough eyeballs to remain secure) or the https://github.com/crev-dev/cargo-crev project (manually reviewed code) also mentioned. It's interesting that they mention C/C++ just rely on distros providing dynamic libs instead which means you don't even control your dependencies versions, some distro does (how reliable is the distro?)... I wonder if that could work for other languages or if it's just as painful as it looks in the C world.
-
I don't care about cookies” extension bought by Avast, users jump ship
For instance, the worst company imaginable may be in charge of software that was once FOSS, and they may change absolutely nothing about it, so it should be fine. However, if a small update is added that does something bad, you should know about it immediately.
The solution seems to be much more clearly in the realm of things like crev: https://github.com/crev-dev/cargo-crev/
Wherein users can get a clear picture of what dependencies are used in the full chain, and how they have been independently reviewed for security and privacy. That's the real solution for the future. A quick score that is available upon display everytime you upgrade, with large warnings for anything above a certain threshold.
-
I think there should be some type of crates vertification especially the popular ones?
The metrics on crates.io are a useful sniff test, but ultimately you need to review things yourself, or trust some contributors and reviewers. Some projects, like cargo crev or cargo vet can help with the process.
-
[Discussion] What crates would you like to see?
You can use cargo-geiger or cargo-crev to check for whether people you trusted (e.g. u/jonhoo ) trust this crate.
-
Pip and cargo are not the same
There is a similar idea being explored with https://github.com/crev-dev/cargo-crev - you trust a reviewer who reviews crates for trustworthiness, as well as other reviewers.
- greater supply chain attack risk due to large dependency trees?
-
Why so many basic features are not part of the standard library?
[cargo-crev](https://github.com/crev-dev/cargo-crev) looks like a good step in the right direction but not really commonly used.
-
“You meant to install ripgrep”
'cargo crev' makes this kind of workflow possible: https://github.com/crev-dev/cargo-crev
-
Difference between cargo-vet and cargo-crev?
The crev folks themselves are no fans of PGP but need a way to security identify that you are in fact the review author, so that's where the id generation comes in. Ultimately crev is just a bunch of repos with text files you sign with IDs. The nice property is that you can chain these together into a web of trust and it's unfortunate that vet doesn't just use the same signed files on repos model as a foundation because even if they don't trust anyone else, we could turn around and trust them.
What are some alternatives?
chalk - 🖍 Terminal string styling done right
crates.io - The Rust package registry
GHSA-5rqg-jm4f-cqx7
stackage - Stable Haskell package sets: vetted consistent packages from Hackage
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
crates.io-index - Registry index for crates.io
SES-shim - Endo is a distributed secure JavaScript sandbox, based on SES
serde - Serialization framework for Rust
wasi-libc - WASI libc implementation for WebAssembly
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
proposal-built-in-modules
Rustup - The Rust toolchain installer