crev
conductor
crev | conductor | |
---|---|---|
12 | 39 | |
387 | 12,999 | |
1.8% | - | |
1.8 | 8.4 | |
over 2 years ago | 5 months ago | |
Java | ||
- | 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.
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.
-
50% new NPM packages are spam
Looks like there's an implementation of it for npm: https://github.com/crev-dev/crev
I've been willing to try it for a while for Rust projects but never committed to spend the time. Any feedback?
-
NPM repository flooded with 15,000 phishing packages
If you don't know the author, signatures do nothing. Anybody can sign their package with some key. Even if you could check the author's identity, that still does very little for you, unless you know them personally.
It makes a lot more sense to use cryptography to verify that releases are not malicious directly. Tools like crev [1], vouch [2], and cargo-vet [3] allow you to trust your colleagues or specific people to review packages before you install them. That way you don't have to trust their authors or package repositories at all.
That seems like a much more viable path forward than expecting package repositories to audit packages or trying to assign trust onto random developers.
[1]: https://github.com/crev-dev/crev [2]: https://github.com/vouch-dev/vouch [3]: https://github.com/mozilla/cargo-vet
-
Dozens of malicious PyPI packages discovered targeting developers
I don't think it makes much sense to verify pypi authors. I mean you could verify corporations and universities and that would get you far, but most of the packages you use are maintained by random people who signed up with a random email address.
I think it makes more sense to verify individual releases. There are tools in that space like crev [1], vouch [2], and cargo-vet [3] that facilitate this, allowing you to trust your colleagues or specific people rather than the package authors. This seems like a much more viable solution to scale trust.
[1]: https://github.com/crev-dev/crev
-
The Python Package Index (PyPI) warns of an ongoing phishing campaign to steal developer credentials and distribute malicious updates.
Crev?
-
Vetting the Cargo
Alternatives to cargo-vet that has been mentioned before here on HN:
- https://github.com/crev-dev/crev
- https://github.com/vouch-dev/vouch
Anyone know of any more alternatives or similar tools already available?
- Crev – Socially scalable Code REView and recommendation system
-
Compromising Angular via expired NPM publisher email domains
I plug this every time, but here goes: https://github.com/crev-dev/crev solves this by providing code reviews, scales via a web-of-trust model, and relies on cryptographic identities. That way, you can depend on a package without having to trust its maintainers and all future versions.
-
Attempt at building a multi-platform UI project (with cross-compiling)
I understand your worries about the number of dependencies you're "forced" to use, however, most of them tend to be doing something that's both non-trivial and useful for more than a single project. As for being able to trust all your transitive dependencies, well, that's something that the Crev project is trying to address, although I don't believe that has gained much traction yet.
-
CII' FOSS best practices criteria
It's good that having a reproducible build process is a requirement for the Gold rating, as is signed releases.
Perhaps there needs to be a Platinum level which involves storing the hash of each release in a distributed append-only log, with multiple third parties vouching that they can build the binary from the published source.
Obviously I'm thinking of something like sigstore[0] which the Arch Linux package ecosystem is being experimentally integrated with.[1] Then there's Crev for distributed code review.[2]
[0] https://docs.sigstore.dev/
[1] https://github.com/kpcyrd/pacman-bintrans
[2] https://github.com/crev-dev/crev
conductor
- Netflix Conductor OSS discontinued support
-
Orkes Monthly Highlights - October 2023
We celebrated a remarkable milestone in September when the Netflix Conductor GitHub repository reached 10k stars. It was a momentous achievement for our DevRel team. Just a month later, we're thrilled to announce that we've surpassed 12k stars! ⭐🎉
-
4 Microservice Patterns Crucial in Microservices Architecture
Also, don’t forget to give us a ⭐ on our Netflix Conductor repo.
-
The Workflow Pattern
One of my favorite workflow engines that has a really simple way to do things was not listed here, so I'll call it out - Netflix Conductor (https://github.com/Netflix/conductor).
Its capabilities comes to light when you model really complex workflows and one real value is how its all very visual not just during modeling but when running it. The history remains visible and you can even see how the whole flow evolved.
-
Orkes Monthly Highlights - September 2023
Yet another significant milestone on our journey: we've proudly reached the 10,000-star mark on our Netflix Conductor GitHub repository! 🌟
-
question about microservice to microservice internal only communication
Give something like https://github.com/Netflix/conductor a try to solve this -- makes it very easy to do what you are trying to achieve.
- Framework used by Netflix to orchestrate microservices
-
Background Task Management on Celery and EC2
Checkout Conductor https://github.com/Netflix/conductor which is far more scalable and easy on the resources with its own Celery like queues. Fully supports writing task workers in python:
- Implementing Saga Pattern in Go Microservices
- GitHub - Netflix/conductor: Microservices orchestration engine.
What are some alternatives?
pacman-bintrans - Experimental binary transparency for pacman with sigstore and rekor
camunda-demo - 🗞️ Repo for this series: https://dev.to/tgotwig/getting-started-with-camunda-spring-boot-2gbi
auto-crev-proofs
Activiti - Activiti is a light-weight workflow and Business Process Management (BPM) Platform targeted at business people, developers and system admins. Its core is a super-fast and rock-solid BPMN 2 process engine for Java. It's open-source and distributed under the Apache license. Activiti runs in any Java application, on a server, on a cluster or in the cloud. It integrates perfectly with Spring, it is extremely lightweight and based on simple concepts.
awesome-security-GRC - Curated list of resources for security Governance, Risk Management, Compliance and Audit professionals and enthusiasts (if they exist).
kestra - Infinitely scalable, event-driven, language-agnostic orchestration and scheduling platform to manage millions of workflows declaratively in code.
secimport - eBPF Python runtime sandbox with seccomp (Blocks RCE).
proposals - Temporal proposals
cargo-vet - supply-chain security for Rust
akhq - Kafka GUI for Apache Kafka to manage topics, topics data, consumers group, schema registry, connect and more...
W4SP-Stealer - w4sp Stealer official source code, one of the best python stealer on the web [GET https://api.github.com/repos/loTus04/W4SP-Stealer: 403 - Repository access blocked]
Springy-Store-Microservices - Springy Store is a conceptual simple μServices-based project using the latest cutting-edge technologies, to demonstrate how the Store services are created to be a cloud-native and 12-factor app agnostic. Those μServices are developed based on Spring Boot & Cloud framework that implements cloud-native intuitive, design patterns, and best practices.