0.2.6 • Published 8 months ago

veracode-ci v0.2.6

Weekly downloads
50
License
MIT
Repository
github
Last release
8 months ago

Gitpod Ready-to-Code

Veracode CI

Goal: Provide a command-line tool to use in NPM scripts for triggering Veracode scans in a CI/CD setting.

Usage

Prerequisites

  • Have VERA_ID and VERA_KEY environment variables defined with valid Veracode API Credentials

Setup in NPM Project 1. Install as a dev dependency

```bash
npm i -D veracode-ci
```
  1. In the scripts block of your package.json, add a veracode script
    {
        ...
        "scripts": {
            ...
            "veracode": "veracode --sandbox --appName=<your-veracode-app-name>"
        },
        ...
    }
  2. Run the veracode script
    npm run veracode

Excluding Folders/Files

Additionally, you can specify your own excludes. By default, this package zips up everything in the current-working-directory of your project (where the package.json is) excluding the node_modules folder. You can overwrite this excludes by adding a comma-delimited value like so:

veracode --sandbox --appName=<your-veracode-app-name> --excludes='node_modules/**/*,lib/**/*'

Command-line Options

FLAGVALUEDESCRIPTION
sandboxnoneTrigger a veracode scan in a sandbox under a provided (existing) app
excludescomma-delimited stringOverride what folders/files are excluded from the project for scanning. Defaults to node_modules/**/*.
appIdintegerVeracode App ID to run the scans under. Must have appId OR appName specified
appNamestringVeracode App Name to run the scans under. Must have appId OR appName specified
scanAllNonfatalTopLevelModulestrue or falseSee Veracode doc for beginprescan.do
autoScantrue or falseSee Veracode doc for beginprescan.do

Useful Resources

0.2.6

8 months ago

0.2.5

8 months ago

0.2.3

4 years ago

0.2.4

4 years ago

0.2.2

4 years ago

0.2.1

4 years ago

0.1.0

4 years ago

0.0.0

4 years ago