Package Exports

create-security-alert-issue

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (create-security-alert-issue) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

create-security-alert-issue

[GitHub] Create an issue from security alert's url.

Install

Install with npm:

npm install create-security-alert-issue --global

Usage

    Usage
      $ create-security-alert-issue <github-security-alert-url>
 
    Inputs
      <github-security-alert-url> GitHub Security Alert URL(open|closed)
 
    Options
      --dryRun Dry-Run when it is enabled
      --token  GitHub Token, or support environment variables - GITHUB_TOKEN=xxx
      --assignees assignee user name. names are separated ,
      --labels    label name. labels are separated , 
      
    Examples
      $ GITHUB_TOKEN=xxx create-security-alert-issue "https://github.com/azu/github-webhook-SecurityVulnerability-test/network/alert/package-lock.json/axios/open"
      $ GITHUB_TOKEN=xxx create-security-alert-issue "https://github.com/azu/github-webhook-SecurityVulnerability-test/network/alert/package-lock.json/axios/open" --labels "security,package"

Changelog

See Releases page.

Running tests

Install devDependencies and Run npm test:

npm test

Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, please create an issue.

Fork it!
Create your feature branch: git checkout -b my-new-feature
Commit your changes: git commit -am 'Add some feature'
Push to the branch: git push origin my-new-feature
Submit a pull request :D

JSPM