Libraries tagged by site wide

Magento module that moves rendering of swatches from JavaScript to PHP for better frontend performance.

Go to Download

A jQuery augmented PHP library for creating and validating HTML forms

Go to Download

Easy Laravel Server-Side implementation of PrimeVue Datatables

Go to Download

Convert Symfony constraints into data-attributes for client-side validation with Parsley.

Go to Download

A server side calculated field for Laravel Nova

Go to Download

This package makes validation rules defined in laravel work client-side by converting to html/js plugins such as jquery validation. It also allows to use laravel validation messages so you can show same messages for both sides.

Go to Download

A Laravel facade/wrapper for the matomo/matomo-php-tracker for server side Matomo tracking.

Go to Download

🚀 A Laravel package that focuses on minimizing payload size of HTML document and optimizing processing on the browser when rendering the web page.

Go to Download

Use noUiSlider Side by side with your filament apps

Go to Download

A Symfony bundle that allows you to track your visitors server side instead of client side

Go to Download

# Introduction Welcome to the Passbase Verifications API docs. This documentation will help you understand our models and the Verification API with its endpoints. Based on this you can build your own system (i.e. verification) and hook it up to Passbase. In case of feedback or questions you can reach us under this email address: [[email protected]](mailto:[email protected]). A User submits a video selfie and valid identifying __Resources__ during a __Verification__ guided by the Passbase client-side integration. Once all the necessary __Resources__ are submitted, __Data points__ are extracted, digitized, and authenticated. These Data points then becomes part of the User's __Identity__. The User then consents to share __Resources__ and/or __Data points__ from their Identity with you. This information is passed to you and can be used to make decisions about a User (e.g. activate account). This table below explains our terminology further. | Term | Description | |-----------------------------------------|-------------| | [Identity](#tag/identity_model) | A set of Data points and Resources related to and owned by one single User. This data can be accessed by you through a Verification. | | Data points | Any data about a User extracted from a Resource (E.g. Passport Number, or Age). | | [Resource](#tag/resource_model) | A source document used to generate the Data points for a User (E.g. Passport). | | [User](#tag/user_model) | The owner of an email address associated with an Identity. | | Verification | A transaction through which a User consents to share Data points with you. If the Data points you request are not already available in the User's Identity, the Passbase client will ask the User to submit the necessary Resource required to extract them. | | Re-authentication (login) | A transaction through which a User can certify the ownership of Personal data previously shared through an Authentication. | # Authentication There are two forms of authentication for the API: • API Key • Bearer JWT Token

Go to Download

Server-side code highlighting with cached results.

Go to Download

Instant Analytics brings full Google GA4 server-side analytics support to your Twig templates and automatic Craft Commerce integration

Go to Download

Simple ESI (Edge Side Include) writer helper

Go to Download

Packege for rendering JavaScript in Laravel application

Go to Download