event-stream
colors.js
event-stream | colors.js | |
---|---|---|
5 | 52 | |
2,157 | 5,153 | |
- | - | |
0.0 | 0.0 | |
over 5 years ago | 11 months ago | |
JavaScript | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
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.
event-stream
-
I gave commit rights to someone I didn't know
Another possible outcome of "I gave commit rights to someone I didn't know": https://github.com/dominictarr/event-stream/issues/116
- Looking for open source Python lite wallet or Payment Processor with unified API for BTC, LTC, ETH, XMR, maybe others
-
What NPM Should Do Today to Stop a New Colors Attack Tomorrow
Whole npm ecosystem is so fragile.
Remember event-stream[1]? Did we learned something from that? Yes, we might. So was it improved? Never. People are still installing 'new' colors package and wondering why its texts are broken.
What if he uploaded malicious code rather than just just gibberish?
[1]: https://github.com/dominictarr/event-stream/issues/116
- NPM Audit: Broken by Design
-
Researcher hacks over 35 tech firms by creating public NPM packages
foo-bar version 1.0 depends on bada-boom 1.0 which depends on bada-bing 1.0. Now you update to foo-bar 1.1 because of some critical update, which in itself now depends on bada-boom 2.0 and bada-bing 2.0. But unbeknownst to you and the author of foo-bar, the bada-boom and bada-bing project was taken over by another maintainer who made an update, but also added some trojan horse code to specifically attack certain users, which was obfuscated and remained undetected. Which has happened before - not just browser extensions are affected by malicious attackers taking over useful projects.
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?
What are some alternatives?
enquirer - Stylish, intuitive and user-friendly prompts, for Node.js. Used by eslint, webpack, yarn, pm2, pnpm, RedwoodJS, FactorJS, salesforce, Cypress, Google Lighthouse, Generate, tencent cloudbase, lint-staged, gluegun, hygen, hardhat, AWS Amplify, GitHub Actions Toolkit, @airbnb/nimbus, and many others! Please follow Enquirer's author: https://github.com/jonschlinkert
chalk - 🖍 Terminal string styling done right
cli - the package manager for JavaScript
GHSA-5rqg-jm4f-cqx7
proposal-built-in-modules
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
pkg-vuln-collab-space - Project for work on improved Package Vulnerability Management & Reporting
SES-shim - Endo is a distributed secure JavaScript sandbox, based on SES
django-money - Money fields for Django forms and models.
wasi-libc - WASI libc implementation for WebAssembly
LADX-Disassembly - Disassembly of Legend of Zelda: Links Awakening DX