Libraries tagged by roller

A multi-source Laravel log file viewer for Livewire, built on top of livewire-datatable — real search/sort/pagination/export instead of hand-rolled pagination, per-entry detail in a Modal, redaction of sensitive data, and a purge action that's actually permission-gated and backed up.

Go to Download

Append-only, branch-aware revision models for Laravel Eloquent. Records are never updated in place - every change is a new row, so history is permanent and any revision can be rolled back.

Go to Download

Connect brokerage accounts to your app for live positions and trading. ## Rate limiting Two limits apply to requests signed with your `clientId`. The stricter one wins, and exceeding either returns `429 Too Many Requests`. - **Customer-level** — 250 requests/minute by default, scoped to your `clientId` and applied across all endpoints. Reported in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. - **Account-level** — 10 requests/minute per account, scoped to (`clientId`, `accountId`). All covered operations for one account draw on the same bucket — reading balances and reading positions share it — and enforcement does not depend on the HTTP method, so updating an account consumes the same bucket as reading it. Only enforced for Personal users, and only for integrations it has been rolled out to — it is not yet in force for every Personal integration. It also does not apply on every operation that documents a 429 below. Where it applies it is reported in `X-RateLimit-Account-Limit`, `X-RateLimit-Account-Remaining` and `X-RateLimit-Account-Reset`. Do not read the absence of those headers as proof the limit is off — some configurations omit the rate limit headers while still enforcing the limit, so header absence tells you nothing about your allowance. On a 429, `X-RateLimit-Remaining: 0` means you hit the customer-level limit and `X-RateLimit-Account-Remaining: 0` means the account-level one. Wait for the corresponding `*-Reset` value (seconds) before retrying, or fall back to exponential backoff with jitter. Not every 429 is explained by those headers. A separate per-authenticated-user limit, reported in no `X-RateLimit-*` header, covers OAuth-authenticated requests and signed requests in configurations where the customer-level limit is not in effect — on the operations that use the default throttles. A few operations override those and are governed by the customer-level limit alone. The two do not stack: a signed request governed by the customer-level limit above is not additionally subject to the per-user one. If a 429 arrives with no header at zero — or with no `X-RateLimit-*` headers at all — honour `Retry-After` and back off. Treat the remaining counts as a hint, not a guarantee that the next request will succeed. Because the customer-level limit applies everywhere, any signed request can return 429. **OAuth-authenticated requests are an exception.** They are not subject to the customer-level limit and do not receive `X-RateLimit-Limit`, `X-RateLimit-Remaining` or `X-RateLimit-Reset` — do not wait on those headers or design around a customer-level allowance on this path. The account-level limit still applies to them on the account-data endpoints above, reported in the `X-RateLimit-Account-*` headers. On operations using the default throttles the per-user limit above applies to them as well, so an OAuth request can be rejected while the account headers still show capacity; on the few operations that override those throttles, OAuth callers have no per-user ceiling at all. Drive retries from `Retry-After` and exponential backoff with jitter rather than from the headers. See https://docs.snaptrade.com/docs/ratelimiting.

Go to Download

Laravel wrapper for the Nager.Date API

Go to Download

User Role and Right Management With Route

Go to Download

Go to Download

Go to Download

Go to Download

Quicksilver implementation to sanitize a production database when it is rolled back to a prior environment.

Go to Download

Native confetti celebrations for NativePHP Mobile — a custom EDGE element backed by Konfetti (Jetpack Compose) on Android and a hand-rolled SwiftUI particle system on iOS.

Go to Download

Add eloquent model events fired after a transaction is committed or rolled back

Go to Download

Legend Has It's MCP content connector for WordPress: OAuth 2.1 server, MCP/JSON-RPC transport, and a registry-driven validated write engine. Extracted from the Cube starter theme so it can be versioned and rolled across the fleet.

Go to Download

A fork of the WordPress filters hook system rolled in to a class to be ported into any PHP-based system

Go to Download

A fork of the WordPress filters hook system rolled in to a class to be ported into any PHP-based system

Go to Download

Prevent stray mails from your laravel application

Go to Download