Installation
The package is published on Packagist, so a plain composer require installs it:
Requirements
The package declares the following constraints in its composer.json:
| Requirement | Constraint | Why | ||||
|---|---|---|---|---|---|---|
| PHP | ^8.2 | Uses readonly properties, constructor promotion, first-class callable syntax. | ||||
ext-sodium | * | libsodium powers Backup\BackupCipher (sealed boxes, secretstream, Argon2id). | ||||
ext-curl | * | Backs the default Http\CurlHttpClient transport. | ||||
psr/log | `^1.0 \ | \ | ^2.0 \ | \ | ^3.0` | The only PSR contract used: Reporter accepts an optional LoggerInterface. |
The package is MIT-licensed and ships under minimum-stability: stable. There are no framework dependencies, not Laravel, not Symfony, nothing beyond the PSR logger interface and the two extensions above.
Autoloading
Classes are autoloaded via PSR-4:
So QuietGuard\Monitor\Config lives at src/Config.php, QuietGuard\Monitor\Http\CurlHttpClient at src/Http/CurlHttpClient.php, and so on.
Installing transitively
If you use one of the official adapters, the Laravel SDK, the Symfony bundle or the WordPress plugin, you do not install this package directly: it is pulled in as a dependency and wired for you. Install quiet-guard/monitor-php on its own only when you are integrating Quiet Guard into a custom PHP application or your own framework. Continue with Configuration.
You are reading the PHP Core v1.0 documentation.