react.dev
The React documentation website
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/reactjs/react.dev with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/reactjs/react.dev'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/reactjs-react-dev)HTML
<a href="/listings/reactjs-react-dev"><img src="/api/listings/reactjs-react-dev/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Prerequisites
1. Git 1. Node: any version starting with v16.8.0 or greater 1. Yarn: See [Yarn website for installation instructions](https://yarnpkg.com/lang/en/docs/install/) 1. A fork of the repo (for any contributions) 1. A clone of the [react.dev repo](https://github.com/reactjs/react.dev) on your local machine
Installation
1. `cd react.dev` to go into the project root 3. `yarn` to install the website's npm dependencies
Running locally
1. `yarn dev` to start the development server (powered by [Next.js](https://nextjs.org/)) 1. `open http://localhost:3000` to open the site in your favorite browser
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 64 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # react.dev
- This repo contains the source code and documentation powering [react.dev](https://react.dev/).
- ## Getting started
- ### Prerequisites
- 1. Git
- 1. Node: v24 or greater
- 1. Yarn Classic: See [Yarn website for installation instructions](https://classic.yarnpkg.com/en/docs/install/)
- 1. A fork of the repo (for any contributions)
- 1. A clone of the [react.dev repo](https://github.com/reactjs/react.dev) on your local machine
- ### Installation
- 1. `cd react.dev` to go into the project root
- 2. `git remote add my-fork-name https://github.com/YOUR_USERNAME/react.dev.git` to add your fork as a remote. Replace `YOUR_USERNAME` with your GitHub username. You only need to do this once.
- 3. `yarn` to install the website's npm dependencies
- ### Running locally
- 1. `yarn dev` to start the development server (powered by [Next.js](https://nextjs.org/))
- 1. `open http://localhost:3000` to open the site in your favorite browser
- ## Contributing
- ### Guidelines
- The documentation is divided into several sections with a different tone and purpose. If you plan to write more than a few sentences, you might find it helpful to get familiar with the [contributing guidelines](https://github.com/reactjs/react.dev/blob/main/CONTRIBUTING.md#guidelines-for-text) for the appropriate sections.
- ### Create a branch
- 1. `git checkout main` from any folder in your local `react.dev` repository
- 1. `git pull origin main` to ensure you have the latest main code
- 1. `git checkout -b the-name-of-my-branch` (replacing `the-name-of-my-branch` with a suitable name) to create a branch
- ### Make the change
- 1. Follow the ["Running locally"](#running-locally) instructions
- 1. Save the files and check in the browser
- 1. Changes to React components in `src` will hot-reload
- 1. Changes to markdown files in `src/content` will hot-reload
- 1. If working with plugins, you may need to remove the `node_modules/.cache/react-docs-mdx` directory and restart the server
- ### Test the change
- 1. If possible, test any visual changes in all latest versions of common browsers, on both desktop and mobile.
- 2. Run `yarn check-all`. (This will run Prettier, ESLint and validate types.)
- ### Push it
- 1. `git add -A && git commit -m "My message"` (replacing `My message` with a commit message, such as `Fix header logo on Android`) to stage and commit your changes
- 1. `git push my-fork-name the-name-of-my-branch`
- 1. Go to the [react.dev repo](https://github.com/reactjs/react.dev) and you should see recently pushed branches.
- 1. Follow GitHub's instructions.
- 1. If possible, include screenshots of visual changes. A preview build is triggered after your changes are pushed to GitHub.
- ## Translation
- If you are interested in translating `react.dev`, please see the current translation efforts [here](https://react.dev/community/translations).
- ## License
- Content submitted to [react.dev](https://react.dev/) is CC-BY-4.0 licensed, as found in the [LICENSE-DOCS.md](https://github.com/reactjs/react.dev/blob/main/LICENSE-DOCS.md) file.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.