All Projects → bitExpert → phing-securitychecker

bitExpert / phing-securitychecker

Licence: Apache-2.0 license
[DEPRECATED] Security Checker Phing Task

Programming Languages

PHP
23972 projects - #3 most used programming language

Projects that are alternatives of or similar to phing-securitychecker

security-advisories
👮 Security advisories of Nextcloud
Stars: ✭ 35 (+133.33%)
Mutual labels:  security-advisories
gemnasium-db
GitLab 依赖项扫描的咨询数据库,每天17:00自动更新
Stars: ✭ 28 (+86.67%)
Mutual labels:  security-advisories
Securityadvisories
🔐 Security advisories as a simple composer exclusion list, updated daily
Stars: ✭ 2,279 (+15093.33%)
Mutual labels:  security-advisories
advisories
Advisories and Proofs of Concept by BlackArrow
Stars: ✭ 17 (+13.33%)
Mutual labels:  security-advisories

phing-securitychecker

A Phing task for interacting with the SensioLabs Security Advisories Checker to check if your application uses dependencies with known security vulnerabilities.

Build Status Coverage Status

Installation

The preferred way of installing bitexpert/phing-securitychecker is through Composer. Add bitexpert/phing-securitychecker as a dependency to composer.json:

composer.phar require --dev bitexpert/phing-securitychecker

Example

Import the default build.xml to let Phing know about the Security Checker task:

    <import file="vendor/bitexpert/phing-securitychecker/build.xml" />

If you imported the default build.xml, you are able to define the lock file path as well the as the webservice endpoint by defining two properties in your main build.xml file:

    <property name="securitychecker.lockfile" value="composer.lock" />
    <property name="securitychecker.endpoint" value="https://security.symfony.com/check_lock" />

Or define the securitychecker task on your own:

     <taskdef name="securitychecker" classname="bitExpert\Phing\SecurityChecker\SecurityCheckerTask" />

Call the task from your build target:

    <securitychecker lockfile="composer.lock" />

License

phing-securitychecker is released under the Apache 2.0 license.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].