COMMUNITY CORRECTIONS

Help make the record accurate.

Maintainers and readers are welcome to challenge a classification or improve its scope.

Open an issue ↗ Browse the repository ↗

What to include

  1. The project name and record ID.
  2. The affected version, platform, and update channel.
  3. What the current description gets wrong, and your proposed replacement.
  4. Source or documentation links that support the correction.

Proposing a pull request

Each record has its own JSON file in the repository’s data directory. Use the record’s edit link, propose a change, and open a pull request. Keep the historical tier separate from a revised assessment. Accepted corrections rebuild the website after review and merge.

A newly discovered security issue should first go through the affected project’s private security reporting process. This study’s public correction tracker is for discussing published records.