wg-best-practices-os-developers
criticality_score
Our great sponsors
wg-best-practices-os-developers | criticality_score | |
---|---|---|
14 | 12 | |
604 | 1,274 | |
5.3% | 1.3% | |
9.7 | 8.5 | |
2 days ago | 4 days ago | |
JavaScript | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wg-best-practices-os-developers
-
Compiler Options Hardening Guide for C and C++
https://github.com/ossf/wg-best-practices-os-developers/issu...
The idea of using `-fsanitize-minimal-runtime` is interesting. I don't have any direct experience with that option. I've created an issue to investigate maybe adding that to the guide. Thanks for the tip!
-
OSCM: The Open Source Consumption Manifesto
These are technical details that are out of the scope of this article, but we think that it is important to mention them because the security strategy of a company should be based on a solid foundation, and these frameworks show that there are already some good starting points, companies don't have to start from scratch. If you want to know more about them or other ways to improve the security of your software supply chain, visit the OpenSSF website.
-
Best practices for effective attack surface analysis
Participating in the cybersecurity community can be a useful way to gain information about security trends and possible risks. Organizations such as the OWASP, OpenSSF, SANS Institute, and ISC2 promote the exchange of information between organizations and can raise the alarm about emerging issues or hacking strategies.
-
Wake-up call: why it's urgent to deal with your hardcoded credentials
Today corporations, open source projects, nonprofit foundations, and even governments are all trying to figure out how to improve the global software supply chain security. While these efforts are more than welcome, for the moment, there is hardly any straightforward way for organizations to improve on that front.
- 'Securing Open Source Software Act' Introduced to US Senate
-
Great Time at JavaZone 2022
Cross industry best practices - openssf.org
- Ask HN: Who is hiring? (June 2022)
-
runk
The Open Source Security Foundation is the continuation(?) of the group CII that was originally founded after this mess came to light. Can't say anything about the salary, but they're currently hiring for a few positions.
-
Ask HN: Is funding the actual problem for healthy Open Source?
TL;DR: Is there any data to suggest that funding an Open Source project materially benefits the users of that project? If you know of any, please share!
This is a question that has been on my mind ever since Log4Shell. I want to know if funding could have an impact on preventing major vulnerabilities or if the issue is something else (lack of guidance for projects, too many cooks, rampant dev ADHD, etc).
It seems like a lot of people are talking about this[0][1] and how funding Open Source would help, but I'm concerned that it's simply wishful thinking that money alone would solve the problem. Sometimes reality is cruel like that.
Is it possible that more funding would help prevent the next Log4Shell or Heartbleed? Maybe! Or are we simply touting a solution, without any data, and our hubris could actually end up hurting security further by just having companies "wash their hands" of responsibility? If FAANG/Fortune 500 throws money over the fence at developers, how much of that money will actually translate into improving the Open Source software?
I personally believe that funding would _help_ with the security of Open Source software. And it would also help with documentation, support, and a number of other "health problems", all of which would likely help with security. But I'm also concerned that this could backfire too in spectacular ways (increased library proliferation to get funding, people pocketing it for a vacation, hackers targeting popular, dormant libs to harvest money from them, etc).
I'm not aware of any actual research/data to provide evidence around improving Open Source security. That's why I wanted to ask y'all. Hacker News is a pretty small community and I wouldn't be surprised if somebody from OpenSSF[2] chimed in to help answer this, lol.
Beyond funding, there are also some projects that I've found like CHAOSS[3][4] that seem to be thinking about quantifying risk for Open Source dependencies and other problems like the "bus factor". It doesn't matter if you fund a project if the dev behind it MIA.
If this data doesn't exist, then it's something that I'll likely start investing my time into generating. (I'm working on some Open Source tooling for dealing with managing dependency security[5] that follows up the Log4Shell tooling we also built[6], which is why this has been on my mind a lot recently.)
Anyway, if you're interested in brainstorming about this further, please shoot me an email (on my profile). Cheers!
0: https://www.wsj.com/articles/protect-open-source-software-prevention-oss-public-use-cybersecurity-innovation-cyberattack-apache-log4j-11643316125
1: https://blog.google/technology/safety-security/making-open-source-software-safer-and-more-secure/
2: https://openssf.org/
3: https://chaoss.community/
4: https://chaoss.community/wp-content/uploads/2021/10/English-Release-2021-10-21.pdf
(Search for "Business Risk" or use the Nav to find the section about how they're attempting to measure the security of Open Source packages)
5: https://github.com/lunasec-io/lunasec/tree/master/lunatrace
(This is under active development and is something that is a week or two away from being polished enough for serious usage.)
6: https://github.com/lunasec-io/lunasec/tree/master/lunatrace/cli/cmd/log4shell
-
Can Some one here verify whether it is true or false? I saw this passage on Quora. It looks Kinda funny to me.
https://openssf.org/ "OSTIF enhances security for users everywhere. We do this through security reviews. (...) reviews have resulted in hundreds of bug patches, including over 20 with a Critical or High severity."
criticality_score
-
Open source public fund experiment - One and a half years update
TL;DR: I could extend the Criticality Score algorithm with usage metrics from Ecosyste.ms API and apply it to all open source accounts under the Open Collective, so we have a new ranking now! I also made it possible to change the weights of each parameter so that you can try the algorithm by yourself.
-
Discover Awesome Python projects
As mentioned in the description, the score is based on the OpenSSF criticality score. I dropped some of the features that are difficult to get from GitHub due to crawl limits, as well as changing some weights.
I posted this last year and have added a lot of new functionality since then: category filtering, similar libraries, pypi & arxiv links, an "importance" score (based on the OpenSSF criticality score), and many more useful libraries
-
'Securing Open Source Software Act' Introduced to US Senate
LF OpenSSF "criticality score" for 100,000 Github repos, https://github.com/ossf/criticality_score & https://docs.google.com/spreadsheets/d/1uahUIUa82J6WetAqtxCM...
> Generate a criticality score for every open source project. Create a list of critical projects that the open source community depends on. Use this data to proactively improve the security posture of these critical projects ... A project's criticality score defines the influence and importance of a project. It is a number between 0 (least-critical) and 1 (most-critical). It is based on the following algorithm by Rob Pike
Top 20 projects:
> node, kubernetes, rust, spark, nixpkgs, cmsSW, tensorflow, symfony, DefinitelyTyped, git, azure-docs, magento2, rails, ansible, pytorch, PrestaShop, framework, ceph, php-src, linux
- Google wants to work with government to secure open-source software
-
[Share my program] Best golang projects display web as a opensource project.
It is possible that in the future expansion, I will also introduce some popularity algorithms to help judge a project instead of just using the number of stars. For example: criticality_score (github.com)
What are some alternatives?
tz - Time zone database and code
tpm2-tss - OSS implementation of the TCG TPM2 Software Stack (TSS2)
aper - A Rust data structure library built on state machines.
AutoGPT - AutoGPT is the vision of accessible AI for everyone, to use and to build on. Our mission is to provide the tools, so that you can focus on what matters.
bicep - Bicep is a declarative language for describing and deploying Azure resources
zotero - Zotero is a free, easy-to-use tool to help you collect, organize, annotate, cite, and share your research sources.
Zulip - Zulip server and web application. Open-source team chat that helps teams stay productive and focused.
Plausible Analytics - Simple, open source, lightweight (< 1 KB) and privacy-friendly web analytics alternative to Google Analytics.
ysoserial - A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.
serverless-graphql - Serverless GraphQL Examples for AWS AppSync and Apollo
PostHog - 🦔 PostHog provides open-source product analytics, session recording, feature flagging and A/B testing that you can self-host.
criticality_score - Gives criticality score for an open source project