attestation
reactjs.org
attestation | reactjs.org | |
---|---|---|
3 | 69 | |
197 | 9,124 | |
3.2% | - | |
8.6 | 9.8 | |
8 days ago | about 1 year ago | |
Go | TypeScript | |
GNU General Public License v3.0 or later | Creative Commons Attribution 4.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.
attestation
-
Gittuf – a security layer for Git using some concepts introduced by TUF
It's multi-pronged and I imagine adopters may use a subset of features. Broadly, I think folks are going to be interested in a) branch/tag/reference protection rules, b) file protection rules (monorepo or otherwise, though monorepos do pose a very apt usecase for gittuf), and c) general key management for those who primarily care about Git signing.
For those who care about a and b, I think the work we want to do to support [in-toto attestations](https://github.com/in-toto/attestation) for [SLSA's upcoming source track](https://github.com/slsa-framework/slsa/issues/956) could be very interesting as well.
- NPM Provenance Public Beta
-
There is no “software supply chain”
I have. I actually worked a few desks down from dpc when he was creating it and we talked about it at length. I felt then and now that it has good goals but a very limiting implementation in that it does not pursue a portable spec and instead anchors a very opinionated format to git, and github, instead of cryptographic keys held in hardware owned controlled by reviewers. I want to see the same keys that sign git commits also sign reviews, for instance.
I think for broad adoption a review system should ask essentially the same questions as crev, but store them in a format like in-toto including signatures by the reviewers created with a user choice of pgp smartcards, ssh keys, or webauthn devices. These reviews would be anchored to hashes of a particular state of a particular tree of code and not to any type of VCS or distribution system. Important code is distributed via Perforce, mercurial subversion, and tar files depending if we are talking about big corps, or linux distro building blocks. A good OSS review system should be also be usable by teams in their internal proprietary codebases too if we wish to see wide adoption. Even for OSS we may wish to share some reviews as standalone objects privately while security embargos are in place, etc. Proofs should also be verified standalone easily from local cache, when github is down, when original repos vanish, etc.
Something that meets these broader needs will make it easy for large orgs with very different internal setups to participate and play nice with other supply chain efforts by the OpenSSF using in-toto for reproducible builds, etc.
My experience tells me we need something much more ambitious than crev, but crev proved to me many people have real interest in this problem which I really thank dpc for.
The biggest blocker for starting this project is the human review spec settling in in-toto https://github.com/in-toto/attestation/issues/77
reactjs.org
-
New React docs pretend SPAs don't exist anymore
yes, he advocated for Vite in his pr: https://github.com/reactjs/reactjs.org/pull/5487
-
Everything You Need to Know About the Updated React Docs
There have been several calls recently to remove the CRA recommendation, perhaps most notably from popular Twitter use and YouTuber Theo (t3.gg) whose pull request on the reactjs project recommending the replacement of CRA with Vite went viral on Twitter. This sparked heated criticism of CRA, including its perceived lack of features (such as native support for TypeScript or popular CSS library Tailwind), size, performance, and more.
-
Introducing react.dev: the new React docs site!
It’s built on Next with tailwind. Check out the beta directory here: https://github.com/reactjs/reactjs.org
-
React.dev
Not Docusaurus, but the source is here:
https://github.com/reactjs/reactjs.org (currently in the "beta" directory)
-
Setup React and Tailwind - The Easy Way
This came up a couple of weeks ago due to a PR opened on the CRA repo asking to kinda deprecate it as the main choice for new React projects. I couldn't help but share my opinion on this as well:
- Proposal to replace create-react-app
- Replace Create React App Recommendation with Vite by T3dotgg · Pull Request
-
Dan Abramov's Response on History and Future of CRA
https://github.com/reactjs/reactjs.org/pull/5487#issuecommen...
I remember submitting the full link. Dunno why it was edited
-
Dan Abramov discusses create-react-app's future
More specifically, the comment: https://github.com/reactjs/reactjs.org/pull/5487#issuecommen...
- Dan Abramov: extensive response on the history and future of Create React App
What are some alternatives?
malicious-software-packages-dataset - An open-source dataset of malicious software packages found in the wild, 100% vetted by humans.
react - Cheatsheets for experienced React developers getting started with TypeScript
root-signing
rabbitmq-website - RabbitMQ website
dsse - A specification for signing methods and formats used by Secure Systems Lab projects.
React - The library for web and native user interfaces.
gittuf - A security layer for Git repositories
snapcraft.io - The official website's repository for the Snap store
packj - Packj stops :zap: Solarwinds-, ESLint-, and PyTorch-like attacks by flagging malicious/vulnerable open-source dependencies ("weak links") in your software supply-chain
control-flag - A system to flag anomalous source code expressions by learning typical expressions from training data
fulcio - Sigstore OIDC PKI
petite-vue - 6kb subset of Vue optimized for progressive enhancement