Libraries tagged by widevine

PHP-Client which enables you to seamlessly integrate the Bitmovin API into your existing projects

Go to Download

Shaka PHP is a library that uses Shaka Packager for DASH and HLS packaging and encryption, supporting Common Encryption for Widevine and other DRM Systems.

Go to Download

Implement the Widevine License Protocol in PHP.

Go to Download

Drop-in fork of tales-from-a-dev/tailwind-merge-php with a widened psr/simple-cache constraint so it can coexist with Craft Commerce (which transitively pins psr/simple-cache ^1.0 via ibericode/vat).

Go to Download

Drop-in fork of gehrisandro/tailwind-merge-php with a widened psr/simple-cache constraint so it can coexist with Craft Commerce (which transitively pins psr/simple-cache ^1.0 via ibericode/vat).

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

Biblioteca PHP para consulta de CEP utilizando múltiplos provedores

Go to Download

Go to Download

Go to Download

Go to Download

Selectel Cloud Storage API

Go to Download

Reviewable Polymorphic Eloquent Models for Laravel 5

Go to Download

Associate files with Eloquent models

Go to Download

Add tags and taggable behaviour to your Laravel app

Go to Download

Use PHP traits to extend Laravel Eloquent Models to allow Tags. Models can be marked as Taggable.

Go to Download