-
Notifications
You must be signed in to change notification settings - Fork 73
WG Quartly Update: 2025-Q4 Securing Critical Projects #535
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
Open
jeffmendoza
wants to merge
3
commits into
ossf:main
Choose a base branch
from
jeffmendoza:patch-3
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.
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 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,111 @@ | ||
| # 2025 Q4 Securing Critical Projects Working Group | ||
|
|
||
| ## Overview | ||
|
|
||
| Most activity under Malicious Packages project. Criticality score continues to run. | ||
|
|
||
| [2025-Q3 Update](2025-Q3-SCP-WG.md) | ||
|
|
||
| ## Identifying Critical Projects | ||
|
|
||
| ### Purpose | ||
|
|
||
| Open Source Software has long suffered from a "tragedy of the commons" | ||
| problem. Organizations large and small make use of OSS every day, but many | ||
| projects are struggling for the time, resources and attention they need. | ||
|
|
||
| This is a resource allocation problem - and we can help solve it together. We | ||
| need ways to connect critical projects we all rely on with organizations that | ||
| can provide them with support. | ||
|
|
||
| [MVSR Link](https://github.com/ossf/wg-securing-critical-projects/blob/main/MVSR.md) | ||
|
|
||
| ### Current Status | ||
|
|
||
| - Nothing currently active | ||
| - Recurring discussions on new methodology enhancing the current set with metadata | ||
|
|
||
| ### Up Next | ||
|
|
||
| - | ||
|
|
||
| ## Criticality Score | ||
|
|
||
| ### Purpose | ||
|
|
||
| 1. Generate a criticality score for every open source project. | ||
|
|
||
| 1. Create a list of critical projects that the open source community depends | ||
| on. | ||
|
|
||
| 1. Use this data to proactively improve the security posture of these critical | ||
| projects. | ||
|
|
||
| ### Current Status | ||
|
|
||
| - Run not working regularly, but get a successful run here and there | ||
| - Looking to see how could be used in LFX insights | ||
|
|
||
| ### Up Next | ||
|
|
||
| - Improve reliability | ||
|
|
||
| ## Package Analysis | ||
|
|
||
| ### Purpose | ||
|
|
||
| The Package Analysis project analyses the capabilities of packages available on | ||
| open source repositories. The project looks for behaviors that indicate | ||
| malicious software: | ||
|
|
||
| - What files do they access? | ||
| - What addresses do they connect to? | ||
| - What commands do they run? | ||
|
|
||
| The project also tracks changes in how packages behave over time, to identify | ||
| when previously safe software begins acting suspiciously. | ||
|
|
||
| This effort is meant to improve the security of open source software by | ||
| detecting malicious behavior, informing consumers selecting packages, and | ||
| providing researchers with data about the ecosystem. | ||
|
|
||
| ### Current Status | ||
|
|
||
| - No major updates | ||
|
|
||
| ## Malicious Packages | ||
|
|
||
| ### Purpose | ||
|
|
||
| Malicious Packages is a collection of reports of malicious packages identified in | ||
| Open Source package repositories, consumable via the Open Source Vulnerability | ||
| (OSV) format. | ||
|
|
||
| The aim of this project and repository is to be a comprehensive, high quality, open source database of reports of malicious packages published on open source package repositories. | ||
|
|
||
| These public reports help protect the open source community, and provide a data source for the security community to improve their ability to find and detect new open source malware. | ||
|
|
||
| ### Current Status | ||
|
|
||
| - Regular submissions and activity | ||
| - Split from Package Analysis, now own project. Project docs updated | ||
| - Working on basic site for viewing JSON stats | ||
| - Adding support for malicious git repositories | ||
|
|
||
| ### Up Next | ||
|
|
||
| - Promotion/outreach | ||
|
|
||
| ## OSTIF Managed Audit Program | ||
|
|
||
| ### Current Status | ||
|
|
||
| - Multiple security audit results released | ||
| - Published OpenSSF Security Scorecard Audit Results! https://openssf.org/blog/2025/10/10/openssf-scorecard-audit-is-complete/ | ||
| - Published "The Bridge to Improving Security: How OSTIF Helps Foundations" https://ostif.org/ostif-helps-foundations/ | ||
| - Published a supplemental Documentation Audit for PHP: https://ostif.org/php-documentation-audit-complete/ | ||
| - Published results for the GNU libmicrohttpd2 Audit: https://ostif.org/gnu-libmicrohttpd2-audit-complete/ | ||
|
|
||
| ### Up Next | ||
|
|
||
| - | ||
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.
Can you describe the underlying issue of this problem? Is it the infrastructure, code, external factors? I am curious what could be done about it.
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.
A bit of all three, external quota issues, infra costs, and code issues. More investigation is needed to nail down each one. It is working "enough" that not much attention is being paid currently.
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.
Thank you!