Skip to content

Commit 96e4bfb

Browse files
author
Lucas Hoffmann
committed
Doc: mention the signing key for phars
The signing key used for the phars is mentioned in the README. This can serve as a "trust anchor" for consumers.
1 parent 7fb9515 commit 96e4bfb

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,9 @@ php phpcs.phar -h
4646
php phpcbf.phar -h
4747
```
4848

49+
These Phars are signed with the official Release key for PHPCS with the
50+
fingerprint `95DE 904A B800 754A 11D8 0B60 5E6D DE99 8AB7 3B8E`.
51+
4952
### Composer
5053
If you use Composer, you can install PHP_CodeSniffer system-wide with the following command:
5154
```bash
@@ -71,8 +74,8 @@ You will then be able to run PHP_CodeSniffer from the vendor bin directory:
7174
### Phive
7275
If you use Phive, you can install PHP_CodeSniffer as a project tool using the following commands:
7376
```bash
74-
phive install phpcs
75-
phive install phpcbf
77+
phive install --trust-gpg-keys 95DE904AB800754A11D80B605E6DDE998AB73B8E phpcs
78+
phive install --trust-gpg-keys 95DE904AB800754A11D80B605E6DDE998AB73B8E phpcbf
7679
```
7780
You will then be able to run PHP_CodeSniffer from the `tools` directory:
7881
```bash

0 commit comments

Comments
 (0)