porro / laravel-connector

v0.1.4 2026-10-20 14:47 UTC

Requires

• php: ^8.2
• illuminate/console: ^11.0|^12.0|^13.0
• illuminate/http: ^11.0|^12.0|^13.0
• illuminate/support: ^11.0|^12.0|^13.0
• porro/php-core: ^0.1.2

Requires (Dev)

• laravel/pint: ^1.18
• orchestra/testbench: ^9.0|^10.0|^11.0
• pestphp/pest: ^3.0|^4.0

MIT

• security
• monitoring
• laravel
• porro

Published on Packagist.org on 2026-10-20 14:47 UTC

README

Read-only Porro connector for Laravel 11–13. It sends one signed report about your site to Porro on the scheduler. It never changes the site and never accepts commands: Porro never connects in.

Install

composer require porro/laravel-connector
php artisan porro:connect <site key>

Copy the site key from the site's page in Porro. porro:connect writes PORRO_KEY to .env and sends the first report.

Reports then go every 15 minutes on Laravel's scheduler, which needs one cron line. If the scheduler isn't already running, porro:connect offers to add it to the server's crontab for you, with the right PHP binary and project folder. If it can't, it prints the line to paste into Forge, Ploi or crontab -e. Use --cron to add it without asking (handy in provisioning scripts) or --no-cron to leave the crontab alone. Skipped it, or connected from another machine? Run php artisan porro:cron on the server; it needs no key.

On Laravel Cloud and Vapor the platform runs the scheduler for you, so there's no cron line: turn the scheduler on (Cloud) or leave it on (Vapor), and set PORRO_KEY as an environment variable.

Add php artisan porro:report to your deploy script so Porro hears about deploys straight away.

Using Filament or Statamic? Install porro/filament-connector or porro/statamic-connector instead. They include this package.

What leaves a site

• Laravel, PHP and package versions (names and versions from composer.lock; the list is only sent when the lock file changes)
• The environment name, and whether debug mode is on (true or false, never the value of any setting)
• Scheduler heartbeat, failed jobs in the last 24 hours, pending migrations
• Newest backup date from spatie/laravel-backup and check results from spatie/laravel-health, if installed

What never does

Content, customer or user data, environment values or secrets. Run php artisan porro:status --json to see the exact report your site would send.

Commands

Command	Does
porro:connect <key>	Saves the key, sends the first report and sets up cron (--cron, --no-cron)
porro:cron	Adds the scheduler to the crontab on its own, no key needed
porro:report	Sends a report now (--packages forces the package list)
porro:status	Shows what the next report contains (--json for the raw report)

Config

Env	Default
PORRO_KEY		The site key
PORRO_INTERVAL	15	Minutes between reports
PORRO_ENABLED	true	Turn reporting off, e.g. on staging

Developing

composer install
composer test

Security

Please email [e-mail] rather than opening an issue. We reply within one working day.

License

MIT