Libraries tagged by installed

Adds ability for users to add their Web3 address into their profile if they have the Polkadot JS extension installed.

Go to Download

Ask Composer which version of a package has been installed

Go to Download

Manage globally installed Composer packages via composer.json with ccu.

Go to Download

A Laravel package to ReCompose your installed packages, their dependencies, your app & server environment

Go to Download

This is .htaccess files for setup, in which WordPress is installed in a wp-core directory and wp-content directory is moved outside a core directory.

Go to Download

GTK 4 bindings for PHP: desktop applications written in PHP against the native GTK 4 API. Installed with PIE (pie install php-gtk4/php-gtk4); the IDE/PHPStan stubs are the separate php-gtk4/stubs package.

Go to Download

Checks, if there are updates available for installed extensions and sends an email

Go to Download

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download

Reports a Laravel app's installed Composer dependencies to NoDisrupt, so its packages can be matched against known vulnerabilities. For apps that can't be versioned remotely (Laravel Cloud, Vapor, Forge, self-hosted).

Go to Download

Automatic loading `bootstrap.php` packages installed using composer for MODX Revolution

Go to Download

Composer command for only auditing installed or updated packages in composer.lock

Go to Download

Static libxlsxwriter-backed NDJSON-to-xlsx binary, installed automatically via a Composer plugin.

Go to Download

Configure your freshly installed laravel project with Vue, Inertia, and Tailwind css using vite as frontend tooling

Go to Download

Creates a relatedPosts field in Post type with wp-graphql. You must have installed wp-graphql and YARPP.

Go to Download

User interface for lavary/crunz. Integrate Crunz library and funtions: Tabular, monthly or weekly interface to view the scheduled and executed tasks. Quick display of the execution result of the tasks that have been executed (Indicator icons easily show the result). Upload, download, edit or delete tasks. Forced run of the task, even outside the scheduled time with eventual display of the log once the execution is completed. It can be used with integrated Crunz or with a version of Crunz already installed on the system

Go to Download