Hi all,

I'm from openEuler security team. We're an open source community aiming to build a secure and trusted linux distro. We're currently building our security database and exporting security advisories in OSV Schema.

[Edit] Full advisories are now in the openEuler repo: https://repo.openeuler.org/security/data/osv/

We would like OSV to validate and ingest our data, and we're ready to discuss the remaining onboarding steps.

Thanks for your consideration! Any suggestions would be greatly appreciated.

Tony

• Prepare your data - refer to the OSV Schema documentation for information on how to properly format the data so it can be accepted.

• Create a PR to reserve an ID prefix and define a new ecosystem (example). We review the records you start publishing for OSV Schema correctness and quality as part of reviewing and merging this PR. [add openEuler ecosystem ossf/osv-schema#358]

• Prepare and publish your records via a Git repository (example). If this method isn’t ideal, we also support publishing records from REST API endpoints or through a GCS bucket(example). (https://repo.openeuler.org/security/data/osv/)

• To support API querying, please create a PR to extend purl_helpers.py and create a new ecosystem in _ecosystems.py. You can refer to existing examples showing how to implement support for Semver and non-Semver ecosystems. [feat: support openeuler ecosystem #3777 ]

• Create a PR to start importing the records you are publishing into our test instance of OSV.dev and validate everything is working as intended there. [feat: add openEuler to test environment #3779 ]

• Create a PR to start importing the records you are publishing into our production environment [feat: add openEuler to production environment #3778 ]