cli
scorecard
cli | scorecard | |
---|---|---|
12 | 25 | |
360 | 4,147 | |
0.3% | 2.6% | |
8.8 | 9.7 | |
4 days ago | 6 days ago | |
JavaScript | Go | |
MIT License | 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.
cli
-
Securizing your GitHub org
📢 By the way NodeSecure CLI has a first-class support of the scorecard.
-
JS-X-Ray 6.0
Those information are visible in the NodeSecure CLI interface:
-
📦 Everything you need to know: package managers
@nodesecure/cli, a CLI that allow you to deeply analyze the dependency tree of a given package or local Node.js project
-
Announcing NodeSecure Vulnera
Fun fact: its first contribution 🐤 on NodeSecure was also on the old version of the code Scanner that managed vulnerabilities.
- GitHub - NodeSecure/cli: JavaScript security CLI that allow you to deeply analyze the dependency tree of a given package or local Node.js project.
-
A technical tale of NodeSecure - Chapter 2
When NodeSecure was a single project the AST analysis was at most a few hundred lines in two or three JavaScript files. All the logic was coded with if and else conditions directly in the walker 🙈.
-
NodeSecure - What's new in 2022 ?
View on GitHub
-
Detect Marak Squires packages with NodeSecure
NodeSecure can now detect packages created by Marak and it will generate a global warning ⚠️.
-
Node-Secure v0.9.0
After more than ten long months of work we are finally there 😵! Version 0.9.0 has been released on npm 🚀.
-
Announcing new Node-Secure back-end
Nsecure
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.
What are some alternatives?
catalyst - Catalyst is a set of patterns and techniques for developing components within a complex application.
in-toto - in-toto is a framework to protect supply chain integrity.
rc - NodeSecure runtime configuration
snyk - Snyk CLI scans and monitors your projects for security vulnerabilities. [Moved to: https://github.com/snyk/cli]
ci - NodeSecure tool enabling secured continuous integration
openRiskScore - A python framework for risk scoring
undici - An HTTP/1.1 client, written from scratch for Node.js
cli - Snyk CLI scans and monitors your projects for security vulnerabilities.
estree - The ESTree Spec
harden-runner - Network egress filtering and runtime security for GitHub-hosted and self-hosted runners
js-x-ray - JavaScript & Node.js open-source SAST scanner. A static analyser for detecting most common malicious patterns 🔬.
slsa - Supply-chain Levels for Software Artifacts