[martincostello]

Enrol opentelemetry-dotnet

I have verified each of the following before submitting this project:

• I am a core maintainer of this project.
• I accept the OSS Scanner terms.
• I confirm that I believe my project meets the inclusion criteria and is an established project that users depend on.
• project.yaml follows the README (one project per PR; tools/validate.py passes locally).
• tools/check <name> builds the project, and its tests run in the shell that follows.
• primary_contact must be the email address of the primary security contact.
• There is a Dockerfile that builds the project (required) in one of two places: in the project's repository at the path dockerfile: names, or next to project.yaml in this repo.
• threat_model.md is written for this project (recommended but optional), placed in the same way: in the repository at the path threat_model: names, or next to project.yaml in this repo.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[martincostello]

I have read the CLA Document and I hereby sign the CLA

[martincostello]

recheck

[Copilot]

🟢 Approval recommended

The configuration follows repository requirements and references verified files on the pinned branch.

0 open findings

What changed in this PR

Enrolls opentelemetry-dotnet in OSS Scanner.

Changes:

• Adds repository, security contacts, homepage, and scanner file paths.
• Pins scanning to the main branch.

File	Description
projects/​opentelemetry-dotnet/​project.yaml	Defines the project’s scanner enrollment.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Kielek]

LGTM

[github-actions]

Enrolment triage: projects/opentelemetry-dotnet

Repository: open-telemetry/opentelemetry-dotnet at main · opened by martincostello

	Check	Result
✅	Repository	created 7 years ago, last push 2 days ago
ℹ️	Stars / forks	3,761 stars · 910 forks
ℹ️	Criticality score	0.76 on the OpenSSF scale of 0 to 1 signals created_since 90, updated_since 0, contributor_count 240, org_count 5, commit_frequency 20.2, recent_releases_count 26, closed_issues_count 384, updated_issues_count 409, comment_frequency 2.8, dependents_count 5,711
✅	License	Apache-2.0
✅	Opened by an active maintainer	member of the owning organisation; 100+ commits in the last 12 months; #4 contributor
✅	Contact in SECURITY.md	security@opentelemetry.io is in SECURITY.md of open-telemetry/.github
ℹ️	OSS-Fuzz	no OSS-Fuzz project is for this repository, but opentelemetry there is for https://github.com/open-telemetry/community
✅	.oss-scanner/ in the repository	present (Dockerfile, threat_model.md); Dockerfile at .oss-scanner/Dockerfile
✅	Pull request scope	only this project's directory
✅	tools/validate.py	passes
✅	Checklist	all 8 ticked

_{Automated, from public GitHub data, to help reviewers. Enrolment is decided case by case against the criteria. If you think we got something wrong, please tell us in a reply.}

[Kielek]

OSS-Fuzz - not enabled, there is no support for C#/.NET.
Internally we have some Fuzzing coverage using native .NET tools.