-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to view Security coding standard after Composer install #79
Comments
@dcunited08 The Readme has been updated for changes made in You can use the "old" install instructions from the last release: https://github.com/FloeDesignTechnologies/phpcs-security-audit/tree/2.0.1#install. Alternatively, require the Dealerdirect Composer PHPCS plugin to register the standard with PHPCS (this plugin will be included automatically in the next release) or register the standard with PHPCS manually using something along the lines of |
Hi @jrfnl I am also facing the same issue. I was wondering if you were able to patch this? |
@anshubansal2000 as @jrfnl mentions, you can install Dealer Direct like so:
This worked fine for me |
I was attempting to install this via Composer but it doesn't appear to be correctly registering. Am I missing something?
`$ composer require --dev pheromone/phpcs-security-audit
Using version ^2.0 for pheromone/phpcs-security-audit
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 2 installs, 0 updates, 0 removals
Writing lock file
Generating autoload files
$ ./vendor/bin/phpcs -i
The installed coding standards are PEAR, Zend, PSR2, MySource, Squiz, PSR1 and PSR12`
The text was updated successfully, but these errors were encountered: