Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add SECURITY.md, referencing GitPython's #117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Byron merged 1 commit into gitpython-developers:master from EliahKagan:security
Jan 5, 2025

Conversation

Copy link
Member

@EliahKagan EliahKagan commented Jan 5, 2025

Along with gitpython-developers/smmap#59 and a forthcoming related PR in GitPython, this will fix #116.

Along with gitpython-developers/smmap#59
and a forthcoming related PR in GitPython, this will fix gitpython-developers#116.
EliahKagan added a commit to EliahKagan/GitPython that referenced this pull request Jan 5, 2025
This expands `SECURITY.md` to affirm the claims in the new
`SECURITY.md` files in gitdb and smmap that vulnerabilities found
in them can be reported in the GitPython repository with the same
link as one would use to report a GitPython vulnerability, as well
as to note how the distinction between affected package can be
specified when it is known at the time a vulnerability is reported.
Along with gitpython-developers/smmap#59
and gitpython-developers/gitdb#117, this
fixes gitpython-developers/gitdb#116.
EliahKagan added a commit to EliahKagan/GitPython that referenced this pull request Jan 5, 2025
This expands `SECURITY.md` to affirm the claims in the new
`SECURITY.md` files in gitdb and smmap that vulnerabilities found
in them can be reported in the GitPython repository with the same
link as one would use to report a GitPython vulnerability, as well
as to note how the distinction between affected package can be
specified when it is known at the time a vulnerability is reported.
Along with gitpython-developers/smmap#59
and gitpython-developers/gitdb#117, this
fixes gitpython-developers/gitdb#116.
EliahKagan added a commit to EliahKagan/GitPython that referenced this pull request Jan 5, 2025
This expands `SECURITY.md` to affirm the claims in the new
`SECURITY.md` files in gitdb and smmap that vulnerabilities found
in them can be reported in the GitPython repository with the same
link as one would use to report a GitPython vulnerability, as well
as to note how the distinction between affected package can be
specified when it is known at the time a vulnerability is reported.
Along with gitpython-developers/smmap#59
and gitpython-developers/gitdb#117, this
fixes gitpython-developers/gitdb#116.
Copy link
Member

@Byron Byron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thank you!

EliahKagan reacted with thumbs up emoji
@Byron Byron merged commit 6fdd19c into gitpython-developers:master Jan 5, 2025
7 checks passed
@EliahKagan EliahKagan deleted the security branch January 5, 2025 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Byron Byron Byron approved these changes

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Unclear what security policy would apply to gitdb and smmap vulnerabilities
2 participants

AltStyle によって変換されたページ (->オリジナル) /