[ihrishikesh0896]

Enrol projects/vulnreach

I have verified each of the following before submitting this project (tick each box by changing [ ] to [x]):

• 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.

To sign the CLA, post a comment on this pull request that contains only this line: I have read the CLA Document and I hereby sign the CLA

To change an enrolment, edit project.yaml; to pause reports, set disabled: true; to withdraw the project, remove projects/<name>/.

Context (optional): OWASP VulnReach is an official OWASP project: a reachability-aware SCA tool (FastAPI server + CLI) that proves which dependency CVEs are actually reachable. Its .oss-scanner/Dockerfile and threat_model.md are being added in OWASP/VulnReach#5.

🤖 Generated with Claude Code

[github-actions]

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

[github-actions]

Enrolment triage: projects/vulnreach

Repository: OWASP/VulnReach at main · opened by ihrishikesh0896

	Check	Result
⚠️	Repository	under 6 months old (created 3 months ago, last push today)
ℹ️	Stars / forks	18 stars · 2 forks · 2 watching
⚠️	Outside participants	1 person from outside the project opened 1 of the last 7 issues and pull requests
⚠️	Criticality score	0.26 on the OpenSSF scale of 0 to 1: low, and the project has under 100 stars signals created_since 8, updated_since 0, contributor_count 4, org_count 1, commit_frequency 1.6, recent_releases_count 5, closed_issues_count 4, updated_issues_count 7, comment_frequency 0.0, dependents_count 20
ℹ️	Package rank	by downloads: nothing from this repository found in the top 15,000 on PyPI or the top 10,000 on npm
✅	License	Apache-2.0
✅	Opened by an active maintainer	collaborator on the repository; 45 commits in the last 12 months; #1 contributor
ℹ️	Contact in SECURITY.md	SECURITY.md gives no email address to check ihrishikeshnate@gmail.com against
ℹ️	OSS-Fuzz	not found in OSS-Fuzz
✅	.oss-scanner/ in the repository	present (Dockerfile, Dockerfile.dockerignore, project.yaml, 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 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.}

[ihrishikesh0896]

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