Giter Site home page Giter Site logo

sast-parser's Introduction

sast-parser

Docker

A simple tool to make understanding GitLab SAST reports a little bit easier.

Installation

pip install -r requirements.txt

Building

docker build -t sast-parser .

Running

From source

usage: parse-sast.py [-h] [--only-severities ONLY_SEVERITIES]
                     [--jsonpath-filter JSONPATH_FILTER]
                     [--no-verify-version]
                     files [files ...]

From docker

docker run --rm -it -v "$(pwd):/reports" sast-parser [-h] [--only-severities ONLY_SEVERITIES]
                     [--jsonpath-filter JSONPATH_FILTER]
                     files [files ...]

You can the create an alias to make it easier to run:

alias sast-parser="docker run --rm -it -v \"$(pwd):/reports\" sast-parser"

sast-parser's People

Contributors

heavensleep avatar lujeni avatar micke90s avatar pcfens avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

sast-parser's Issues

Docker image broken?

can you give an example usage?

docker run --rm -v $(pwd)/gl-sast-report.json:/gl-sast-report.json pcfens/sast-parser /gl-sast-report.json
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/gl-sast-report.json": permission denied: unknown.

maybe CMD in dockerfile should be replaced in ENTRYPOINT

also looks the image on dockerhub is not updated as is from 2 years ago

Kubesec report has been updated to version 15

Hi,

First of all, I would like to thank you for your job! I think this is a missing piece in gitlab!

Gitlab just upgraded kubesec output report version to 15. I have seen in the code that there is an specific check that if version >= 15 the job fails.

I tried to manually change the version to 14 to bypass this verification and everything worked properly.

Is there any additional reason to keep this verification there? Would not make more sense to add this verification as a flag?

Thank you!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.