Download the PHP package alex-kassel/dev-kit without Composer

On this page you can find all versions of the php package alex-kassel/dev-kit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package dev-kit

🛠️ DevKit

Comprehensive development workspace automation and package engineering toolkit for modular Laravel monorepos

Key Features • Requirements • Installation • Usage • Testing • Changelog

Latest Version Laravel Support PHP Support


Key Features


Requirements


Installation

Require alex-kassel/dev-kit as a development dependency in your Laravel project:

Initialize your workspace and install AI agent tooling:

To set up a fresh environment and immediately localize dev-kit for package development:


Usage

Workspace Preparation & Package Discovery

Ingesting & Localizing Packages (pkg:clone)

Safe Package Removal (pkg:remove)

Scaffolding & Quality Assurance

Documentation & Release Pre-flight


AI Agent Integration

dev-kit automatically equips host repositories with standardized agent runbooks and modular skills, working seamlessly alongside Laravel Boost:


Configuration

Publish the configuration file to customize Git patterns and trusted organizations:

Options in config/dev-kit.php:

[!TIP] Zero-Friction Ingestion: pkg:clone automatically falls back to HTTPS if SSH authentication (missing key or host verification) fails. When localizing packages previously installed with fixed SemVer constraints (e.g. ^0.0.2), pkg:sync automatically unbinds the constraint to @dev across require and require-dev to prevent Composer solver conflicts.


Verification and Removal Guarantees

pkg:check runs Composer validation, Pint, PHPStan and tests locally. A selected check that is unavailable or unconfigured produces incomplete, not passed, and a failing exit code. Unknown or empty --only selections are rejected. PHPUnit configurations may be named phpunit.xml or phpunit.xml.dist; an empty suite fails.

pkg:check vendor/package --isolated additionally exports the current Git checkout (tracked and non-ignored files, including tests and uncommitted changes), installs dependencies into a fresh temporary vendor/, and executes that package's declared PHPUnit or Pest runner. It excludes the host autoloader, global Composer configuration, package lock file, .env, Git metadata and existing dependency directories. Path repositories are rejected. Network access and independently resolvable package dependencies are required. Each installation/test process has a ten-minute timeout. Temporary files are removed afterward, including after failure.

This is an installation and executable-test check, not a static proof that every referenced symbol is declared directly or that untested paths are correct. The former regex-based PhantomDependencyDetector API was removed; IsolatedPackageVerifier provides the actual standalone check. pkg:release-check requires all five checks to pass. The standalone copy retains tests marked export-ignore; it is not a validation of the distribution archive's exact contents.

pkg:remove vendor/package --yes confirms deletion while retaining Git checks. --json changes output format only and does not authorize deletion. Without --force, removal refuses non-Git directories, Git errors, missing upstreams, detached HEAD, dirty or ignored files, stashes and local commits not covered by remote tracking refs. These refs reflect the last fetch; removal does not contact remotes. --force bypasses Git preservation checks, never path validation. Linked package directories and traversal arguments are rejected. A manifest failure stops before deletion; a deletion failure restores the original manifest and reports that files may have been partially removed.

--unlink only removes the dependency declaration, retaining files. Neither unlink nor removal runs Composer or changes composer.lock/vendor; reconcile the host installation with Composer afterward. A later pkg:sync can register a retained directory again.

Localization validates versions associated with the current checkout: an explicit manifest version, valid tags pointing at a clean HEAD, and the current branch/its numeric Composer branch alias. Historical tags never certify another checkout. Unknown or incompatible versions stop localization with an actionable message; stability flags such as @dev do not bypass numeric constraints. Composer remains responsible for final dependency resolution.

The network-backed consumer regression suite is separate from the fast local suite:

It proves both successful standalone installation with declared dependencies and failure when a grouped import uses an undeclared Laravel component. CI runs it on the PHP 8.4 / Laravel 13 stable jobs for all three operating systems.


Testing

Run the dev-kit test suite via standard Composer tooling shortcut:

Or run directly via PHPUnit or universal verification:


Changelog

Please see CHANGELOG.md for details on changes in recent releases.


Security Vulnerabilities

Please review Security Policies on how to report vulnerabilities.


License

The MIT License (MIT). Please see LICENSE for license details.


All versions of dev-kit with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
composer-runtime-api Version ^2.1
illuminate/console Version ^11.0 || ^12.0 || ^13.0
illuminate/contracts Version ^11.0 || ^12.0 || ^13.0
illuminate/filesystem Version ^11.0 || ^12.0 || ^13.0
illuminate/process Version ^11.0 || ^12.0 || ^13.0
illuminate/support Version ^11.0 || ^12.0 || ^13.0
symfony/process Version ^7.0 || ^8.0
symfony/filesystem Version ^7.0 || ^8.0
composer/semver Version ^3.4
nunomaduro/termwind Version ^2.0
laravel/boost Version ^2.0
orchestra/testbench Version ^9.0 || ^10.0 || ^11.0
phpunit/phpunit Version ^11.0 || ^12.0
phpstan/phpstan Version ^1.12 || ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package alex-kassel/dev-kit contains the following files

Loading the files please wait ...