Repository navigation
Conversation
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
Enrolment triage:
|
| Check | Result | |
|---|---|---|
| ✅ | Repository | created 12 years ago, last push 4 days ago |
| ℹ️ | Stars / forks | 4,031 stars · 2,017 forks · 347 watching |
| ℹ️ | Outside participants | 37 people from outside the project opened 50 of the last 50 issues and pull requests |
| ℹ️ | Criticality score | 0.70 on the OpenSSF scale of 0 to 1signalscreated_since 210, updated_since 0, contributor_count 757, org_count 8, commit_frequency 6.6, recent_releases_count 14, closed_issues_count 0, updated_issues_count 0, comment_frequency 0, dependents_count 124,832 |
| ℹ️ | Package rank | by downloads: nothing from this repository found in the top 15,000 on PyPI |
| ✅ | License | Apache-2.0 |
| Opened by an active maintainer | no maintainer role visible; 8 commits in the last 12 months; #18 contributor | |
| ℹ️ | Contact in SECURITY.md |
no SECURITY.md to check security@openvswitch.org against |
| OSS-Fuzz | in OSS-Fuzz as openvswitch, whose contacts do not include security@openvswitch.org (its primary contact is blp@ovn.org) |
|
| ℹ️ | .oss-scanner/ in the repository |
not present; the Dockerfile is in this pull request |
| ✅ | Pull request scope | only this project's directory |
| ✅ | tools/validate.py |
passes |
| ✅ | Checklist | all 7 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.
|
@sb- @carlini @punitshah @srxzr-ant @aterzis-ant Hi I am a lawyer for Red Hat where @apconole works and their work on OVS is Red Hat-related. I am wondering why @apconole is being asked to sign the CLA given that @apconole is not actually contributing any code to the repository. Is a submitted project actually being treated in some sense as a "Contribution" under the CLA? Or is signing the CLA basically a formality here that would only get triggered in the event @apconole actually made a substantive contribution of code or documentation etc. to this repository? |
Enrol
projects/<name>I have verified each of the following before submitting this project (tick each box by changing
[ ]to[x]):project.yamlfollows the README (one project per PR;tools/validate.pypasses locally).tools/check <name>builds the project, and its tests run in the shell that follows.primary_contactmust be the email address of the primary security contact.Dockerfilethat builds the project (required) in one of two places: in the project's repository at the pathdockerfile:names, or next toproject.yamlin this repo.To change an enrolment, edit
project.yaml; to pause reports, setdisabled: true; to withdraw the project, removeprojects/<name>/.Context (optional): if you believe it is not obvious why your project qualifies for our inclusion criteria, you may write a brief note here to explain why you feel it does.