Libraries tagged by history.js

Model history tracking dependency for Laravel Enso

Go to Download

Prevent users from reusing recently used passwords

Go to Download

A package to keep a history of all password changes of users

Go to Download

This extension adds storage history of changes to the ActiveRecord model.

Go to Download

Backpack interface for venturecraft/revisionable

Go to Download

CoinPayment is a Laravel module for handling transactions from CoinPayment like a create transaction, history transaction, etc.

Go to Download

Implementation of the Omnibus Directive for Sylius application.

Go to Download

A Guzzle middleware to keep track of redirects

Go to Download

Track Laravel Artisan commands executions inside Laravel Pulse

Go to Download

Model changes history for laravel

Go to Download

An improved history backend module for Neos

Go to Download

PHP client for App Store Server API. Manage your customers’ App Store transactions from your server.The App Store Server API is a REST API that you call from your server to request and provide information about your customers' in-app purchases. The App Store signs the transaction and subscription renewal information that this API returns using the JSON Web Signature (JWS) specification.App Store Server API is independent of the app’s installation status on the customer’s devices. The App Store server returns information based on the customer’s in-app purchase history regardless of whether the customer installed, removed, or reinstalled the app on their devices.To request transaction and subscription status information with this API, provide any original transaction identifier that belongs to the customer. The transaction history API responds with a complete list of transactions, 20 at a time, starting with the oldest first. The subscription status API returns the status for all of the customer’s subscriptions, organized by their subscription group identifier.Use the Send Consumption Information endpoint to send information to the App Store when customers request a refund for a consumable in-app purchase, after you receive the CONSUMPTION_REQUEST App Store server notification. Your data helps inform refund decisions.

Go to Download

REST and CLI API for adding, updating, and deleting records in TYPO3. Tracks relations so records can be inserted in any order. Uses remote ID mapping so you don't have to keep track of what UID a record has gotten after import. Data is inserted using backend APIs as if a real human did it, so you can can inspect the record history and undo actions.

Go to Download

A container for Guzzle history middleware

Go to Download

Log the changed data in frontend mode

Go to Download