<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review

Parts of this issue can initially be left blank to be filled in during the review.

You can delete the comments (or not).
-->

## Project

[{Project Name}]({pmi link})

## Intectual Property Management

- [ ] All project code is correctly licensed
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied
- [ ] All distributed third-party content has been vetted by the IP Due Diligience process (i.e., IP Log has been approved)

## Open Source Rules of Engagement

General:

- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner

Specific:

- [ ] Communication channels advertised
- [ ] Advertised communication channels used
- [ ] Committers are responding to questions
- [ ] Committers are responding to issues
- [ ] Committers are responding to pull/merge/review requests

## Branding and Trademarks

If the project has a custom website...

- [ ] Project website uses the project's formal name in first and all prominent references
- [ ] Project website includes a trademark attribution statement
- [ ] Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)

General:

- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations

## Legal Documentation

Specific files:

- [ ] License files in all repository roots
- [ ] README
- [ ] CONTRIBUTING (or equivalent)
- [ ] NOTICES (or equivalent)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY

Required elements:

- [ ] ECA is referenced/described
- [ ] Security policy is described
- [ ] Build instructions provided

## Metadata

- [ ] The formal name, e.g. Eclipse Foo™, is used in the project title
- [ ] The formal name including appropriate marks is used in the first mention in the text of the project description, and scope
- [ ] The project description starts with a single paragraph that can serve as an executive summary
- [ ] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date

<!-- Quick actions will configure the state of the issue. Leave these. -->
/title "CVE Assignment Request"
/confidential
/label ~"CVE Assignment"
/assign @wbeaton