scorecard
in-toto
scorecard | in-toto | |
---|---|---|
25 | 4 | |
4,147 | 827 | |
2.6% | 0.8% | |
9.7 | 8.9 | |
6 days ago | 10 days ago | |
Go | Python | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
scorecard
-
Can some expert analyze a github repo and tell us if it's really safe or not?
For general open source hygiene, I'd recommend running OpenSSF scorecards on your github repo and following-up on anything it suggests. https://github.com/ossf/scorecard.
-
Securizing your GitHub org
The OSSF scorecard initiative is really good to assess your project against security best practices. I am not the first to write about this.
- OpenSSF Scorecard – Build better security habits, one test at a time
-
You should use the OpenSSF Scorecard
Each area has its own associated risk, so the overall score is the average of the five areas. Here, you can check the details of each by consulting the documentation in detail.
-
Software Supply Chain and Data Infrastructure Security - 5 lessons from AllDayDevOps 2022
Mitigation, according to Sean, is a combination of appropriate (network) access control, SCA (Software Composition Analysis) tooling to manage your policies around CVEs, and purging “all the things”. He also thinks MFA (multi-factor authentication) for authors of (critical) packages should be required. Sean gets his vulnerability insights from deps.dev, ossindex.sonatype, and cvedetails.com, and closely monitors interesting initiatives such as the OpenSSF Security Scorecards - a tool to assess open source projects for security risks through a series of automated checks.
- Boost Your Enterprise Security with GitHub Actions and the OSSF Score Card
- How does your company manage open-source dependencies?
-
Washington, DC, and open—for maintainers
Give feedback on new security standards: The various security standards like OpenSSF Scorecard and SLSA.dev can be a lot to digest, but they are likely going to be very influential in developing government standards. Take a peek at them, and if you have concerns or questions, file issues. The people behind them want to hear from a broad range of maintainers, so your feedback really does matter. (If you're a Tidelift maintainer partner, you can also bring the feedback to us—we are participating in these discussions, and may be able to either point to existing discussions, explain them more deeply, or bring your feedback to the appropriate places.)
-
Episode 102: myNewsWrap – SAP and Microsoft
Security Scorecards
-
Best practices for managing Java dependencies
I recommend using https://deps.dev to get a feeling for what you are bringing into your project. It also integrates with OSSF Scorecards, which gives a good overview over how healthy the project is, and whether it employs industry best practices.
in-toto
-
UEFI Software Bill of Materials Proposal
The things you mentioned are not solved by a typical "SBOM" but e.g. CycloneDX has extra fields to record provenance and pedigree and things like in-toto (https://in-toto.io/) or SLSA (https://slsa.dev/) also aim to work in this field.
I've spent the last six months in this field and people will tell you that this or that is an industry best practice or "a standard" but in my experience none of that is true. Everyone is still trying to figure out how best to protect the software supply chain security and things are still very much in flux.
-
An Overview of Kubernetes Security Projects at KubeCon Europe 2023
in-toto is an open source project that focuses on the attestation part of software supply chain security. You use it to define a “layout” for a project, i.e., how the different components should fit together. A project ships this definition with its code, and then another user of that software can compare what they have with the attached definition to see if it matches the structure and contents they expect. If it doesn’t, then this could point to external tampering or other issues.
-
How do you mitigate supply chain attacks?
But it's not all doom and gloom because the industry is evolving. Companies like Google are formulating tools like scorecard to heuristically reduce risk by encouraging you to rely on trustable dependencies only. There's also more complex tools like in-toto that actually look at the integrity of your supply chain (don't ask me how this one works, I just know that people like it).
- in-toto/in-toto: in-toto is a framework to protect supply chain integrity.
What are some alternatives?
snyk - Snyk CLI scans and monitors your projects for security vulnerabilities. [Moved to: https://github.com/snyk/cli]
openRiskScore - A python framework for risk scoring
ochrona-cli - A command line tool for detecting vulnerabilities in Python dependencies and doing safe package installs
cli - Snyk CLI scans and monitors your projects for security vulnerabilities.
pip-audit - Audits Python environments, requirements files and dependency trees for known security vulnerabilities, and can automatically fix them
harden-runner - Network egress filtering and runtime security for GitHub-hosted and self-hosted runners
macOS-Security-and-Privacy-Guide - Guide to securing and improving privacy on macOS
slsa - Supply-chain Levels for Software Artifacts
i-probably-didnt-backdoor-this - A practical experiment on supply-chain security using reproducible builds
kaniko - Build Container Images In Kubernetes
algo - Set up a personal VPN in the cloud