Popular Packages

  • Blade

    salvatori/alma-one

    WordPress boilerplate with Composer, easier configuration, and an improved folder structure

  • PHP

    funson86/yii2-cms

    Yii2 Cms for other application

  • PHP

    uzdevid/yii2-jwt-auth

    JWT authorization

  • PHP

    bravegeek/allrival-sdk

    An SDK designed for easy usage of the allrival.com website's API

  • PHP

    laravel-admin-reporter/reporter

    Exception reporter for laravel

  • PHP

    richardandrade/php_router

    A simple router for managing your app routes

  • PHP

    kafkiansky/forbid

    A psalm plugin that finds and forbids code smells.

  • PHP

    deepeloper/lib-fs

    File system library

  • PHP

    zellien/zellien-mjml

    PHP library for rendering MJML templates

  • PHP

    ernandesrs/easy-crud

    Features for database manipulation: create, read, update, delete

  • PHP

    jiboule/ddump-bundle

    DDump Bundle to dump and optionnaly exit

    Abandoned! See jiboule/ddump

  • PHP

    alissonlinneker/statuspage-php-sdk

    # Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication <!-- ReDoc-Inject: <security-definitions> -->

  • PHP

    pandishpan/authorized-attributes

    Authorized Model Attributes for Laravel with Model Policies

  • PHP

    sotoro/fpdf

    FPDF Composer Wrapper

  • PHP

    datumsquareit/social-share

    Create posts on social platforms