Download the PHP package apiforge/apiforgephp without Composer
On this page you can find all versions of the php package apiforge/apiforgephp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download apiforge/apiforgephp
More information about apiforge/apiforgephp
Files in apiforge/apiforgephp
Package apiforgephp
Short Description API observability & intelligence for Laravel/PSR-15 — local-first, privacy-first
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package apiforgephp
apiforgephp
API observability & intelligence for Laravel — local-first, privacy-first.
Track latency, error rates, and behavioral trends of your APIs. Everything stays on your machine.
Install
Requires PHP ≥ 8.2 and the
pdo_sqliteextension (php8.x-sqlite3package on Debian/Ubuntu).
Quick start
The service provider is auto-discovered by Laravel. Register the middleware in your bootstrap/app.php (Laravel 11+) or app/Http/Kernel.php (Laravel 10):
That's it. The local dashboard is now live at http://localhost:8000/_apiforge (adjust the port to match your Laravel app).
Dashboard
In local mode, the dashboard is served automatically at /_apiforge on your Laravel app's port — no separate process needed.
- Health Score (0–100) — global API health at a glance
- Latency percentiles — P50 / P90 / P99 per route
- Error rates — 4xx and 5xx breakdown
- Automatic insights — latency anomalies, dead endpoints, release regressions
- Time series chart — click any route to see its latency over time
Configuration
Publish the config file (optional):
Or configure via environment variables:
| Variable | Default | Description |
|---|---|---|
APIFORGE_ENV |
APP_ENV |
Environment label (production, staging…) |
APIFORGE_RELEASE |
APP_VERSION |
Release/version tag for regression tracking |
APIFORGE_SERVICE |
APP_NAME |
Service name |
APIFORGE_SAMPLING |
1.0 |
Sample rate 0.0–1.0 |
APIFORGE_DASHBOARD |
true |
Enable/disable the local dashboard routes |
APIFORGE_DASHBOARD_PREFIX |
_apiforge |
URL prefix for the local dashboard |
APIFORGE_CLOUD_URL |
— | Cloud mode: SaaS API base URL |
APIFORGE_API_KEY |
— | Cloud mode: project API key (af_…) |
Cloud mode
Send metrics to the APIForge SaaS platform instead of storing them locally:
In cloud mode, events are buffered to a local temp file and flushed to the SaaS ingest API every 60 seconds. The local dashboard is disabled automatically.
Release tracking
Set the release tag to enable before/after deployment comparison:
Or dynamically in AppServiceProvider:
When a new release is detected, APIForge compares P90 latency before and after and surfaces regressions automatically.
What you get
- Per-route latency — P50, P90, P99 per endpoint
- Error rate by route — 2xx / 3xx / 4xx / 5xx breakdown
- API Health Score — a single 0–100 score summarising your API's health
- Ghost route detection — requests that match no declared Laravel route
- Latency anomaly alerts — Z-score detection against a 7-day baseline
- Dead endpoint detection — routes with no traffic for 21+ days
- Release regression analysis — automatic P90 comparison per deploy
- Progressive drift detection — slow latency increases over weeks
- Untracked route detection — declared routes that never received traffic
- Inflight concurrency tracking — approximate
inflight_avgandinflight_maxper route
Graceful shutdown
The middleware flushes automatically at the end of every request. No manual teardown is needed for standard PHP-FPM deployments.
For long-running processes (Laravel Octane, FrankenPHP, Swoole), call shutdown() on application termination if needed — the aggregator is otherwise request-scoped and carries no state between requests.
Known limitations
| Limitation | Detail |
|---|---|
| TTFB = total duration | PHP-FPM sends responses atomically — true Time to First Byte cannot be measured at the middleware layer. lat_ttfb_* values equal lat_*. |
| Approximate inflight count | PHP workers are isolated; the inflight counter is shared via a file lock, which is accurate to the order of magnitude but not microsecond-precise. |
Privacy by design
- Request and response bodies are never read
- No PII captured — only route patterns, HTTP methods, status codes, and timing
- Route parameters are normalised (
/users/42→/users/:id, UUIDs →/:uuid) - SQLite database stays entirely on your server in local mode
- Sampling rate can be set below 1.0 to reduce storage footprint
Requirements
- PHP ≥ 8.2
- Laravel ≥ 10.0
ext-pdo_sqlite— install withapt install php8.x-sqlite3if not present
License
MIT — see LICENSE.
All versions of apiforgephp with dependencies
ext-pdo Version *
ext-pdo_sqlite Version *
ext-json Version *