Libraries tagged by ebnf

Roundcube plugin that enforces requirement of solving a Captcha during login

Go to Download

Opinionated Opscale rules for enforcing software architecture guidelines

Go to Download

Composable PHP authorization toolkit — Casbin RBAC enforcer, JWT/OIDC verification (JWKS), fine-grained capabilities, validation rules and ready-to-use HTTP middlewares for API protection.

Go to Download

Opinionated PHP Coding Style enforcement for PHP

Go to Download

SQL database definition differencing tool. Structure and data is defined in a DTD-enforced, human-readable XML format. Outputs transactional SQL statement files to apply your changes.

Go to Download

Laravel package for managing enum-based model states with enforced transitions and automatic status history tracking.

Go to Download

Filament 5 plugin connecting an Eloquent resource to the Celebrimbor visual page builder, with interface contracts enforcing what the model/resource must expose.

Go to Download

A Laravel Redis driver override that enforces clearing of cache using prefixes, rather than a flush

Go to Download

A package for enforcing GDPR compliance rules

Go to Download

Position-blind decision engine for funnypot: cheapest-first decision precedence, learn-then-enforce, pin/TTL deception consistency, report suppression. Returns a Decision; the host adapter executes it.

Go to Download

DTO library in PHP provides benefits such as encapsulating data, enforcing immutability and facilitating data transformation.

Go to Download

Content-Elemente können ganz einfach per Drag & Drop in die Artikel an beliebige Positionen gezogen werden.

Go to Download

TYPO3 extension for the LABOR.digital Factory headless CMS boilerplate — ships Content Blocks, record types, tenant-scope enforcement, and provisioning CLIs for single-tenant and shared-tenant installations.

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

The Jiannius engineering standard, and the machinery that installs and enforces it

Go to Download