This repository contains a Slim Framework CSRF protection PSR-15 middleware. CSRF protection applies to all unsafe HTTP requests (POST, PUT, DELETE, PATCH).

You can fetch the latest CSRF token's name and value from the Request object with its getAttribute() method. By default, the CSRF token's name is stored in the csrf_name attribute, and the CSRF token's value is stored in the csrf_value attribute.

Via Composer

$ composer require slim/csrf

Requires Slim 4.0.0 or newer.

In most cases you want to register Slim\Csrf for all routes, however, as it is middleware, you can also register it for a subset of routes.

use DI\Container
use Slim\Csrf\Guard;
use Slim\Factory\AppFactory;

require __DIR__ . '/vendor/autoload.php';

// Start PHP session
session_start();

// Create Container
$container = new Container

This repository contains a Slim Framework Flash messages service provider. This enables you to define transient messages that persist only from the current request to the next request.

Via Composer

$ composer require slim/flash

Requires Slim 3.0.0 or newer.

This example assumes that you have php-di/php-di installed.

<?php
use DI\ContainerBuilder;
use Slim\Factory\AppFactory;
use Slim\Flash\Messages;
use Slim\Routing\RouteContext;

require_once __DIR__ . '/../vendor/autoload.php';

$containerBuilder = new ContainerBuilder();

// Add container definition for the flash component
$containerBuilder->addDefinitions(
    [
        'flash' => function () {
            $storage = [];
            return new Messages($storage);
        }
    ]
);

AppFactory::setContainer($containerBuilder->build());

$app = AppFactory::create();

// Add session start

Note This is the documentation for Monolog 3.x, if you are using older releases see the documentation for Monolog 2.x or Monolog 1.x

Monolog sends your logs to files, sockets, inboxes, databases and various web services. See the complete list of handlers below. Special handlers allow you to build advanced logging strategies.

This library implements the PSR-3 interface that you can type-hint against in your own libraries to keep a maximum of interoperability. You can also use it in your applications to make sure you can always use another compatible logger at a later time As of 1.11.0 Monolog public APIs will also accept PSR-3 log levels Internally Monolog still uses its own level scheme since it predates PSR-3.

---

^{Sponsored by:}

Better Stack lets you centralize, search, and visualize your logs.

---

Install the latest version with

composer require monolog/monolog

<?php
use

Repository abandoned 2019-12-31

This repository has moved to laminas/laminas-permissions-acl.

Provides a lightweight and flexible access control list (ACL) implementation for privileges management.

• File issues at https://github.com/zendframework/zend-permissions-acl/issues
• Documentation is at https://docs.zendframework.com/zend-permissions-acl/

Guzzle is a PHP HTTP client that makes it easy to send HTTP requests and trivial to integrate with web services.

• Simple interface for building query strings, POST requests, streaming large uploads, streaming large downloads, using HTTP cookies, uploading JSON data etc...
• Can send both synchronous and asynchronous requests using the same interface.
• Uses PSR-7 interfaces for requests, responses, and streams. This allows you to utilize other PSR-7 compatible libraries with Guzzle.
• Supports PSR-18 allowing interoperability between other PSR-18 HTTP Clients.
• Abstracts away the underlying HTTP transport, allowing you to write environment and transport agnostic code; i.e., no hard dependency on cURL PHP streams, sockets, or non-blocking event loops.
• Middleware system allows you to augment and compose client behavior.

$client = new \GuzzleHttp\Client()
$response = $client->request('GET', 'https://api.github.com/repos/guzzle/guzzle');

echo $

Repository abandoned 2019-12-31

This repository has moved to laminas/laminas-xmlrpc.

From its home page, XML-RPC is described as a ”...remote procedure calling using HTTP as the transport and XML as the encoding. XML-RPC is designed to be as simple as possible, while allowing complex data structures to be transmitted, processed and returned.”

Zend\XmlRpc provides support for both consuming remote XML-RPC services and building new XML-RPC servers.

• File issues at https://github.com/zendframework/zend-xmlrpc/issues
• Documentation is at https://docs.zendframework.com/zend-xmlrpc/

• Probably the world's most popular code for sending email from PHP!
• Used by many open-source projects: WordPress, Drupal, 1CRM, SugarCRM, Yii, Joomla! and many more
• Integrated SMTP support – send without a local mail server
• Send emails with multiple To, CC, BCC, and Reply-to addresses
• Multipart/alternative emails for mail clients that do not read HTML email
• Add attachments, including inline
• Support for UTF-8 content and 8bit, base64, binary, and quoted-printable encodings
• SMTP authentication with LOGIN, PLAIN, CRAM-MD5, and XOAUTH2 mechanisms over SMTPS and SMTP+STARTTLS transports
• Validates email addresses automatically
• Protects against header injection attacks
• Error messages in over 50 languages!
• DKIM and S/MIME signing support
• Compatible with PHP 5.5 and later, including PHP 8.2
• Namespaced to prevent name clashes
• Much more!

Many PHP developers need to send email from their code. The only…

A simple library to encode and decode JSON Web Tokens (JWT) in PHP, conforming to RFC 7519.

Use composer to manage your dependencies and download PHP-JWT:

composer require firebase/php-jwt

Optionally, install the paragonie/sodium_compat package from composer if your php env does not have libsodium installed:

composer require paragonie/sodium_compat

use Firebase\JWT\JWT
use Firebase\JWT\Key;

$key = 'example_key';
$payload = [
    'iss' => 'http://example.org',
    'aud' => 'http://example.com',
    'iat' => 1356999524,
    'nbf' => 1357000000
];

/**
 * IMPORTANT:
 * You must specify supported algorithms for your application. See
 * https://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-40
 * for a list of spec-compliant algorithms.
 */
$jwt = JWT::encode($payload, $key, 'HS256');
$decoded = JWT::

Config is a file configuration loader that supports PHP, INI, XML, JSON YML, Properties and serialized files and strings.

Config requires PHP 7.4+.

IMPORTANT: If you want to use YAML files or strings, require the Symfony Yaml component in your composer.json.

The supported way of installing Config is via Composer.

$ composer require hassankhan/config

Config is designed to be very simple and straightforward to use. All you can do with it is load, get, and set.

The Config object can be created via the factory method load(), or by direct instantiation:

use Noodlehaus\Config
use Noodlehaus\Parser\Json;

// Load a single file
$conf = Config::load('config.json');
$conf = new Config('config.json');

// Load values from multiple files
$conf = new Config(['

PHP_CodeSniffer is a set of two PHP scripts; the main phpcs script that tokenizes PHP, JavaScript and CSS files to detect violations of a defined coding standard, and a second phpcbf script to automatically correct coding standard violations. PHP_CodeSniffer is an essential development tool that ensures your code remains clean and consistent.

PHP_CodeSniffer requires PHP version 5.4.0 or greater, although individual sniffs may have additional requirements such as external applications and scripts. See the Configuration Options manual page for a list of these requirements.

If you're using PHP_CodeSniffer as part of a team, or you're running it on a CI server, you may want to configure your project's settings using a configuration file.

The easiest way to get started with PHP_CodeSniffer is to download the Phar files for each of…

A php tool to lint and validate xml files from the commandline.

XML Lint checks the syntax of any xml files and validates the file against the XSD schema defined in the file.

If you'd like to include this library in your project with composer, simply run:

composer require "sclable/xml-lint"

To lint a single xml file:

vendor/bin/xmllint path/to/file.xml

To lint a directory and all its subdirectories:

vendor/bin/xmllint path/to/dir

xmllint has built in cli help screen:

vendor/bin/xmllint --help

• -v be verbose, display the filename of the current file to lint
• -r 0 don't search recursive (if the argument is a directory)
• -e name exclude files or directories containing 'name'
• -s skip the xsd validation

# check code style
php tools/php-cs-fixer/vendor/bin/php-cs-fixer fix --dry-run -v

# run tests
php vendor/bin/phpunit
php vendor/bin/behat

Using docker:

# Example
docker

A compact command line linting tool for validating YAML files, using the parsing facility of the Symfony Yaml Component.

usage: yaml-lint [options] [input source]

  input source    Path to file(s), or "-" to read from standard input

  -q, --quiet     Restrict output to syntax errors
  -h, --help      Display this help
  -V, --version   Display application version

To get started using yaml-lint in a project, install it with Composer:

composer require --dev j13k/yaml-lint

It can then be run from the project's vendor/bin directory.

To set up yaml-lint globally, install it in the Composer home directory:

composer global require j13k/yaml-lint

It can then be run from the bin directory of Composer home (typically ~/.composer/vendor/bin).

A binary edition , yaml-lint.phar, is available for download with each release. This embeds the latest stable version of the Symfony Yaml component that is current at the time of the release.

…

A rule based 'linter' for Dockerfiles. The linter rules can be used to check file syntax as well as arbitrary semantic and best practice attributes determined by the rule file writer The linter can also be used to check LABEL rules against docker images.

• Quickstart
• Extending and Customizing: Rule Files
  • Profile Section
  • General Section
  • Rule Attributes
  • Line Rule Section
  • Required Instruction Section
• Library Usage
  • Node.js application use
  • Command Line use
• Credits
• License

1. Change to directory where you have a Dockerfile
2. run

• Atomic CLI

      atomic run projectatomic/dockerfile-lint
  
      atomic run projectatomic/dockerfile-lint image <imageid>
  

• Docker CLI

      docker run -it --rm -v $PWD:/root/ \
             projectatomic/dockerfile-lint \
             dockerfile_lint [-f Dockerfile]
  
      docker run -it --rm -v $PWD:/root/  \
             -v /var/run/docker.sock:/var/run/docker.sock \
             projectatomic/dockerfile-lint \
             dockerfile_lint  image <imageid>
  

By default, the linter runs in strict mode (errors and/or warnings result in non-zero return code). Run the command with -p or --permissive to…

ShellCheck is a GPLv3 tool that gives warnings and suggestions for bash/sh shell scripts:

The goals of ShellCheck are

• To point out and clarify typical beginner's syntax issues that cause a shell to give cryptic error messages.

• To point out and clarify typical intermediate level semantic problems that cause a shell to behave strangely and counter-intuitively.

• To point out subtle caveats, corner cases and pitfalls that may cause an advanced user's otherwise working script to fail under future circumstances.

See the gallery of bad code for examples of what ShellCheck can help you identify!

• How to use
  • On the web
  • From your terminal
  • In your editor
  • In your build or test suites
• Installing
• Compiling from source
  • Installing Cabal
  • Compiling ShellCheck
  • Running tests
• Gallery of bad code
  • Quoting
  • Conditionals
  • Frequently misused commands
  • Common beginner's mistakes
  • Style
  • Data and typing errors
  • …