Security News
Opengrep Emerges as Open Source Alternative Amid Semgrep Licensing Controversy
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
corp-check-cli
Advanced tools
If you want to use CorpCheck for more than just as a web tool to check packages for risks, you can integrate the CLI module into your build and deployment process to actually prohibit the deployment of risky packages. The CLI will use the ruleset you defi
If you want to use CorpCheck for more than just as a web tool to check packages for risks, you can integrate the CLI module into your build and deployment process to actually prohibit the deployment of risky packages. The CLI will use the ruleset you define and stop if it encounters a viral license, an unreleased package or an abandoned package will tons of open issues.
install to global using npm:
npm install -g corp-check-cli
install to project using npm:
npm install --save-dev corp-check-cli
You can identify risks in published npm packages with corp-check npm <package>
CLI command. And you will know how good that package for you.
corp-check npm express
You can create a report about your product with corp-check <path-to-local-source>
. Also you can use your package-lock.json
with the --package-lock
option. And with --prod
argument you can skip the devDependencies
from validation
corp-check . --package-lock --prod
Define script for corp-check project validation
{
"scripts": {
"corp-check": "corp-check ."
}
}
and you can run by npm
npm run corp-check
Just create a corp-check-rules.json
in your project root and you can override the default evaluation rules. With the --rule-set <path>
option you can have more custom rules.
corp-check . --rule-set ./my-rules.json
If you want to validate an npm package with your custom rule you have to pass the --rule-set
option
corp-check npm express --rule-set ./my-rules.json
You can read more about custom rules here
-V, --version output the version number
--force, -f force validation
--verbose, -v list all warnings
--rule-set <ruleSetJson> validation rule set, default: ./corp-check-rules.json
--log-level <logLevel> winston log level, default: warn
--prod skip devDependencies
--package-lock use package-lock.json file
-h, --help output usage information
FAQs
If you want to use CorpCheck for more than just as a web tool to check packages for risks, you can integrate the CLI module into your build and deployment process to actually prohibit the deployment of risky packages. The CLI will use the ruleset you defi
We found that corp-check-cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.