Download the PHP package derkekser/laravel-paladin without Composer

On this page you can find all versions of the php package derkekser/laravel-paladin. 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 laravel-paladin

Laravel Paladin Banner

🛡️ Laravel Paladin

Autonomous Self-Healing for Laravel Applications

Laravel Paladin is an intelligent Laravel package that monitors your application logs, detects errors, and automatically attempts to fix them using AI-powered code generation. It creates isolated git worktrees for each fix attempt, runs tests to verify the fixes, and creates pull requests when successful.

Inspiration

This package was inspired by Taylor Otwell's demonstration of a self-healing Laravel application at Laracon 2025 in Amsterdam. After seeing the potential of AI-powered autonomous error fixing, I set out to build a practical implementation that any Laravel developer could use in their applications.

Documentation

For full documentation, visit https://derkekser.github.io/laravel-paladin-docs/

Features

Requirements

Installation

1. Install the Package

2. Publish Configuration and Migrations

3. Run Migrations

4. Configure Environment Variables

Add the following to your .env file:

5. Configure Queue (Recommended)

Laravel Paladin runs as a queued job by default. Make sure you have a queue worker running:

Alternatively, configure your queue in config/queue.php to use database, Redis, or another driver.

Usage

Basic Usage

Run the self-healing process:

This will:

  1. Check for OpenCode and install it if needed
  2. Scan your application logs for errors
  3. Use AI to analyze and categorize issues
  4. Create a git worktree for each fix attempt
  5. Generate fixes using OpenCode
  6. Run your test suite to verify the fix
  7. Create a pull request (or send email notification) if successful

Synchronous Mode

To run the healing process synchronously (useful for debugging):

Check Healing Status

View the status of recent healing attempts:

Cleanup Old Worktrees

Clean up old worktrees to free disk space:

Scheduled Healing

Add to your app/Console/Kernel.php to run automatically:

Configuration

The configuration file config/paladin.php provides extensive customization options:

AI Evaluator Configuration

Laravel Paladin supports different AI evaluators and providers:

Evaluators:

Supported Providers (for laravel-ai evaluator):

Example Configurations:

Log Monitoring

Git Configuration

Pull Request Configuration

How It Works

  1. Log Scanning: Paladin scans your configured log channels for errors
  2. AI Analysis: Your configured AI provider analyzes each error and categorizes it by type and severity
  3. Prioritization: Issues are prioritized (critical → high → medium → low)
  4. Worktree Creation: A git worktree is created for isolated fix attempts
  5. AI Prompt Generation: The AI generates a detailed prompt for OpenCode
  6. Code Fixing: OpenCode applies the fix in the worktree
  7. Testing: Your test suite runs to verify the fix
  8. Pull Request: If tests pass, a PR is created (or email sent)
  9. Cleanup: The worktree is removed after completion
  10. Retry: If the fix fails, Paladin retries with a different approach (up to max attempts)

Database Tracking

All healing attempts are tracked in the healing_attempts table:

Security Considerations

Troubleshooting

OpenCode Not Found

Paladin will automatically install OpenCode if it's not found. If installation fails, you can manually install it:

Git Worktree Issues

If worktrees aren't being cleaned up properly:

AI API Errors

Tests Not Running

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

The MIT License (MIT). Please see LICENSE file for more information.

Credits

Support

For general support and questions, please use the GitHub Issues page.


All versions of laravel-paladin with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/contracts Version ^11.0|^12.0
illuminate/support Version ^11.0|^12.0
illuminate/console Version ^11.0|^12.0
illuminate/database Version ^11.0|^12.0
illuminate/queue Version ^11.0|^12.0
laravel/ai Version ^0.3
guzzlehttp/guzzle Version ^7.0
spatie/laravel-package-tools Version ^1.16
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 derkekser/laravel-paladin contains the following files

Loading the files please wait ...