doc-en
cargo-crev
doc-en | cargo-crev | |
---|---|---|
17 | 55 | |
475 | 2,034 | |
1.3% | 1.7% | |
9.8 | 7.7 | |
6 days ago | 3 days ago | |
XML | Rust | |
- | 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.
doc-en
-
TIL about PHP MessageFormatter class and ICU Message Format
Wait, but for as much as just adding an example, isn't it much simpler? I mean, I can just navigate to https://github.com/php/doc-en/blob/master/reference/intl/messageformatter/format-message.xml, edit the existing example and then create a pull request.
-
Top 10 Recommended Books For PHP Developers
But there is. Even better, there is a git repo. Just recently I saw a bad practice of echoing the error message out unconditionally and proposed a fix.
-
An overview of the architecture on which the Radicore framework was built
Pull requests allow people to add changes in a different branch of the code and ask to merge with the master branch. There can be discussion before anything is accepted. If you go back to the php example I linked, there is a small discussion.
-
How to choose between PASSWORD_ARGON2I and PASSWORD_ARGON2ID algos in password_hash()?
The PHP docs are on GitHub: https://github.com/php/doc-en (other languages have their own doc- repos)
-
What is your #1 feature request for 8.2?
Well overhaul documentation is totally possible right now, no need to wait for 8.2. You are welcome to contribute in https://github.com/php/doc-en
-
Searching php.net document is unfriendly for beginners.
It's now all on GitHub (both code and issues), with links at the top of every page (I think those currently still link to bugs.php.net which is actively monitored alongside GitHub issues)
-
comments "on Function Overloading Feature"
fwiw when you made the comment, it wasn't documented that 8.0.0 removed it on the linked-to-page, thanks for making that obvious, just fixed it, https://github.com/php/doc-en/pull/1149
- Are old PHP Manual versions archived somewhere?
-
PHP Docs are awesome - have you ever read them?
For reference, should have included the link: https://github.com/php/doc-en
- PHP.Net Documentation for ext/sodium Coming Soon
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?
serde - Serialization framework for Rust
crates.io - The Rust package registry
phpstorm-stubs - PHP runtime & extensions header files for PhpStorm
stackage - Stable Haskell package sets: vetted consistent packages from Hackage
Halite - High-level cryptography interface powered by libsodium
crates.io-index - Registry index for crates.io
web-php - The www.php.net site
doc-base - Tools for the PHP documentation
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
ddd - Domain Driven Design PHP helper classes
Rustup - The Rust toolchain installer