Libraries tagged by installed

These checks are where you can check if optimizer is installed on your server.

Go to Download

Standalone application with the Laravel Package of Mixpost Lite pre-installed and configured

Go to Download

Standalone application with the Laravel Package of Mixpost Pro Team pre-installed and configured

Go to Download

Implements concrete Queue for the redis work queue. Requires the packages flowpack/jobqueue-common and the redis PHP extension to be installed.

Go to Download

Implements concrete Queue for the doctrine work queue. Requires the packages flowpack/jobqueue-common to be installed.

Go to Download

A tool that shows nova-specific packages installed on your application.

Go to Download

Provides improved naming of transactions, error reporting and general tracking for SilverStripe site's on servers with the New Relic PHP Agent installed. As well as an overview of the Site's Performance.

Go to Download

Allow packages to be installed from a repository or tarball bundle that have multiple packages in the sub-folders

Go to Download

Check the WPScan Vulnerability Database via API to identify the security issues on plugins and WordPress installed.

Go to Download

Composer plugin that provides efficient querying for installed package versions (no runtime IO)

Go to Download

Displays cost/size of each composer package installed.

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

A composer plugin to check that local binaries / executables are installed and are of the correct version before package install.

Go to Download

This plugin collects available ahoy scripts from installed LakeDrops plugins and configures ahy in the project root.

Go to Download

Package that provides an APCu cache backend that falls back to a given fallback if the APCu extension is not installed.

Go to Download