Repository navigation
Enroll pwsafe: Dockerfile, project.yaml, threat_model.md - #1213
Merged
Merged
Conversation
Signed-off-by: ronys <ronys@pwsafe.org>
ronys
requested review from
aterzis-ant,
carlini,
punitshah,
sb- and
srxzr-ant
as code owners
October 29, 2026 08:10
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
|
All contributors have signed the CLA ✍️ ✅ |
Enrolment triage:
|
| Check | Result | |
|---|---|---|
| ✅ | Repository | created 11 years ago, last push today |
| ℹ️ | Stars / forks | 887 stars · 174 forks · 33 watching |
| ℹ️ | Outside participants | 20 people from outside the project opened 33 of the last 100 issues and pull requests |
| ℹ️ | Criticality score | 0.69 on the OpenSSF scale of 0 to 1signalscreated_since 303, updated_since 0, contributor_count 135, org_count 2, commit_frequency 22.5, recent_releases_count 12, closed_issues_count 85, updated_issues_count 88, comment_frequency 1.9, dependents_count 22,359 |
| ℹ️ | Package rank | by downloads: nothing from this repository found in the top 15,000 on PyPI or the top 10,000 on npm |
| License | GitHub cannot name the license; its file says Artistic License 2.0 terms, as follows: |
|
| ✅ | Opened by an active maintainer | member of the owning organisation; 100+ commits in the last 12 months; #1 contributor |
| ℹ️ | Contact in SECURITY.md |
SECURITY.md gives no email address to check security@pwsafe.org against |
| ℹ️ | OSS-Fuzz | not found in OSS-Fuzz |
| ℹ️ | .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 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.
srxzr-ant
approved these changes
Oct 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.threat_model.mdis written for this project (recommended but optional), placed in the same way: in the repository at the paththreat_model:names, or next toproject.yamlin 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 CLATo 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.