Libraries tagged by shared host

Shared database, migration, job queue and event infrastructure for Trilby Media's Grav plugins (SQLite, MySQL, PostgreSQL)

Go to Download

Shared order-hold kernel for Sylius 2: keeps held orders out of the unpaid-orders cancellation, filters payment methods everywhere (shop, API, default method, post-order change) and blocks payment entry, through single decorators and tagged checkers

Go to Download

TYPO3 Forum by coding.ms: A simple forum extension for TYPO3 that lets logged-in users ask questions, post replies, mark questions as answered, and optionally use tags. Access to questions can be restricted through shared user groups when needed. Pro features add notifications and subscriptions for frontend users and administrators.

Go to Download

Cross-cutting platform utilities for Laravel microservices: PostgreSQL FDW migrations helpers, locale providers, shared contracts.

Go to Download

Pomm2 shared elements between Silex and Symfony.

Go to Download

The chassis every Noria Laravel product sits on: workspace tenancy with row level security, RBAC, an audit trail, passwordless auth, database operations, and the shared primitives.

Go to Download

Warren — a Reddit-inspired theme for Flarum 2. Compact post rows with a vote pill, image and text previews, Hot/New/Top sorting, a collapsible rail and threaded comments. Shares fof/gamification's vote tables, so nothing is lost either way.

Go to Download

Functional keyboard shortcuts

Go to Download

Reusable countries and structured postal addresses for Capell: one shared address record, site-scoped, that any package can reference instead of re-modelling location fields.

Go to Download

Core AI abstraction layer for Laravel. Provides shared contracts, managers, retry logic, cost tracking, and CLI tools for building AI provider packages.

Go to Download

Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_). **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body: 1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined to that brand — reads filtered, writes stamped. This is the recommended way to give a single brand's team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual request by sending the brand's id or slug in this header. Most SDKs let you set it once on the client so every call inherits it. A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token. Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide. List endpoints additionally take a `?brandScope=own|shared|both` parameter to narrow further within whichever brand context already applies. `own` returns only rows assigned to that brand, and requires a brand context — a brand-bound token, a resolved brand session, or the `X-Zippendo-Brand` header above — otherwise `400`. `shared` returns only the organization-wide rows (equivalent to filtering `brandId=none`). The default, `both`, keeps the existing behaviour: a brand context sees its own rows plus the organization-wide ones. Set `X-Zippendo-Brand-Scope` as a client default to apply the same choice to every request instead of repeating the query parameter on each call — an explicit `brandScope` query parameter always wins over the header, and a blank header value is ignored. Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan's limit returns `403`.

Go to Download

Extracts images automatically from the first post to display an animated, lazy-loaded thumbnail image slider in the Flarum discussion list using a shared modular layout structure.

Go to Download

Shared AI core on top of laravel/ai: model catalogue with prices, request ledger, executor, queue, cost accounting and batch polling.

Go to Download

WordPress plugin for a widget that displays a list of post with the most shares on Facebook.

Go to Download

Shared Laravel module with modular support for User, Post, Comments, etc.

Go to Download