-
Notifications
You must be signed in to change notification settings - Fork 61
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
Add 2025 Q1 Securing Repos WG update #444
Open
steiza
wants to merge
3
commits into
main
Choose a base branch
from
wg_repos_q1_2025
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+52
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
# 2025 Q1 Securing Software Repositories Working Group | ||
|
||
## Overview | ||
|
||
**Mission**: Improve security of software repositories (npm, PyPI, RubyGems, ...) by providing a forum for discussion, a maturity model for security roadmaps, and guidance for individual security capabilities. | ||
|
||
**Links**: | ||
- [GitHub repository](https://github.com/ossf/wg-securing-software-repos) | ||
- [Slack channel](https://openssf.slack.com/archives/C034CBLMQ9G) | ||
- [WG meeting docs](https://docs.google.com/document/d/18Y8HxntL2RkcgqoFdhdLpj17e4MOSCdskP1IoDiuP1s/edit?usp=sharing) | ||
|
||
## Securing Software Repositories Working Group | ||
|
||
### Purpose | ||
|
||
Improve security of software repositories by providing a forum for discussion, a maturity model for security roadmaps, and guidance for individual security capabilities. | ||
|
||
### Current Status | ||
|
||
- [Central now performs Sigstore Signature Validation](https://central.sonatype.org/news/20250128_sigstore_signature_validation_via_portal/) | ||
- [Posting for technical writer](https://jobs.smartrecruiters.com/LinuxFoundation/744000038830864-openssf-securing-repositories-working-group-technical-writer) to write package yanking guidance is live | ||
- Letter of support to Python Software Foundation's grant request to US National Science Foundation on detecting, flagging, and quarantining malware | ||
- Meetings continue every other week, with async discussions in the Slack channel | ||
|
||
### Up Next | ||
|
||
- Hire contractor; publish package yanking guidance | ||
- [Funding request: UI/UX support for attestations on software repos](https://github.com/ossf/tac/issues/424) | ||
- Continue supporting landing security capabilities in software repositories | ||
|
||
### Questions/Issues for the TAC | ||
|
||
- None at this time | ||
|
||
## RSTUF Project | ||
|
||
### Purpose | ||
|
||
Provide a service to protect repository index from tampering by distributing them with The Update Framework (TUF) | ||
|
||
### Current Status | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. RSTUF is starting the security audit from 3rd February 2025 |
||
- Continuing to work towards v1.0 release to run alongside RubyGems and PyPI and sign their repository index | ||
- [Funding approved: 2025 cloud development costs](https://github.com/ossf/tac/issues/417) | ||
|
||
### Up Next | ||
|
||
- [Security audit with OSTIF](https://github.com/ossf/tac/issues/379) | ||
|
||
### Questions/Issues for the TAC | ||
|
||
- None at this time |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence doesn't actually say what the status is. Did the WG send that letter?