Repository navigation
Enable high-severity private vulnerability reports for Homebrew - #1157
Merged
sb- merged 1 commit intoOct 27, 2026
Merged
Conversation
p-linnane
requested review from
aterzis-ant,
carlini,
punitshah,
sb- and
srxzr-ant
as code owners
October 27, 2026 01:18
|
All contributors have signed the CLA ✍️ ✅ |
Enrolment triage:
|
| Check | Result | |
|---|---|---|
| ✅ | Repository | created 10 years ago, last push today |
| ℹ️ | Stars / forks | 50,116 stars · 11,400 forks · 740 watching |
| ℹ️ | Outside participants | 56 people from outside the project opened 64 of the last 100 issues and pull requests |
| ℹ️ | Criticality score | 0.91 on the OpenSSF scale of 0 to 1signalscreated_since 212, updated_since 0, contributor_count 1,423, org_count 6, commit_frequency 122.9, recent_releases_count 70, closed_issues_count 882, updated_issues_count 891, comment_frequency 1.0, dependents_count 393,618 |
| ℹ️ | Package rank | by downloads: nothing from this repository found in the top 15,000 on PyPI |
| ✅ | License | BSD-2-Clause |
| ✅ | Opened by an active maintainer | merged 12 of the last 100 pull requests; 100+ commits in the last 12 months; #7 contributor |
| ℹ️ | Contact in SECURITY.md |
SECURITY.md of Homebrew/.github gives no email address to check security@brew.sh against |
| ℹ️ | OSS-Fuzz | not found in OSS-Fuzz |
| ✅ | .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 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.
Signed-off-by: Patrick Linnane <patrick@linnane.io>
p-linnane
force-pushed
the
homebrew-private-vulnerability-reports-high
branch
from
October 27, 2026 01:23
f3952c3 to
77fffbe
Compare
sb-
approved these changes
Oct 27, 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/HomebrewI 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.