![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
@jitesoft/audit-for-gitlab
Advanced tools
Minimal application to convert npm audit report into gitlab-ci vulnerability report format.
This is a small script to add a npm audit
GitLab dependency scanner.
It generates a JSON audit via npm and converts it to the format that gitlab expects as dep scan report.
In case a vulnerability equal or higher to moderate
is found, it will exit with exit code 1, i.e., fail.
While generating the report, it will also output number of vulnerabilities found (and types) in stdout.
Observe:
The scanner will currently only work with npmjs versions which makes use of audit report v2.
GitLab report specification supported is 15.0.2
Easiest way to use the scanner is to add it as a include in your .gitlab-ci.yml file, such as:
include:
- https://gitlab.com/jitesoft/open-source/javascript/audit-for-gitlab/raw/master/scan.yml
This will run the scanning on your project on all events as long as it is disabled via env variables.
If you wish to customize it a bit more, you can extend or write your own:
npm-audit_dependency_scanning:
image: registry.gitlab.com/jitesoft/open-source/javascript/audit-for-gitlab:1
script:
- audit-for-gitlab
artifacts:
reports:
dependency_scanning: gl-dependency-scanning-report.json
If you wish to just use the scanner in one of your current scripts, the easiest way to do this, is to just install it via NPM:
npm i --global @jitesoft/audit-for-gitlab
cd /my/project/dir
audit-for-gitlab
cat gl-dependency-scanning-report.json
The dockerfile is rebuilt on each new version of the scanner released, each build is released for ARM64 and AMD64.
The following env variables can be used to configure the behaviour of the application slightly:
SECURE_LOG_LEVEL
- Will change the log level to report more or less output.
Available levels are: fatal
, error
, warn
, info
, debug
though only debug, info and fatal are used in the application.
The debug level is basically only used for debugging purposes and development. info
is default.
SCAN_EXIT_CODE
- Will force a specific exit code in case of a moderate, high or critical vulnerability is found.
In case this is not set, exit code 1
will be used in the cases above, else 0
.
FAQs
Minimal application to convert npm audit report into gitlab-ci vulnerability report format.
The npm package @jitesoft/audit-for-gitlab receives a total of 0 weekly downloads. As such, @jitesoft/audit-for-gitlab popularity was classified as not popular.
We found that @jitesoft/audit-for-gitlab 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
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.