Download the PHP package rafaelogic/codesnoutr without Composer

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

CodeSnoutr - Laravel Code Scanner Package

Latest Version on Packagist Total Downloads PHP Version Require Laravel Tests

A comprehensive Laravel code scanner that detects security vulnerabilities, performance issues, and code quality problems with a modern web interface and AI-powered auto-fix capabilities.

⚠️ Important: This package is designed for local development environments only. It is not recommended for production use.

Image

📚 Table of Contents

✨ Features

🔍 Comprehensive Scanning

🎨 Modern Web Interface

🚀 Flexible Scanning Options

🔧 Developer Integration

🤖 AI Smart Assistant

🤖 AI-Ready Architecture

📋 Requirements

System Requirements

Queue & Cache Requirements (For AI Auto-Fix)

CRITICAL: The AI Auto-Fix and Fix All features require proper queue and cache configuration:

Cache Driver (Required)

Queue Driver (Required)

Queue Worker (Required)

AI Auto-Fix Requirements (Optional)

To use AI-powered automatic fixing:

Frontend Requirements

🚀 Installation

Prerequisites

Before installing CodeSnoutr, ensure your system meets these requirements:

Step 1: Install via Composer

Install the package using Composer:

Step 2: Run Installation Command

Execute the installation command to set up CodeSnoutr:

This interactive installation will:

  1. Publish Configuration: Creates config/codesnoutr.php with default settings
  2. Run Migrations: Sets up database tables for scans, issues, and settings
  3. Publish Assets: Copies CSS and JavaScript files to public/vendor/codesnoutr/
  4. Create Directories: Sets up necessary storage directories
  5. Configure Routes: Registers web and API routes
  6. Set Permissions: Ensures proper file permissions

Step 3: Configure Environment (Optional)

Add CodeSnoutr-specific environment variables to your .env file:

⚠️ Important Cache Configuration

The Fix All Issues feature requires a persistent cache driver to track progress between the queue worker and web interface. The array cache driver will NOT work because it's per-process memory and doesn't share data between processes.

Supported Cache Drivers:

  • ✅ file - Works out of the box, good for development
  • ✅ redis - Best performance, recommended for production
  • ✅ database - Requires php artisan cache:table && php artisan migrate
  • ❌ array - Does NOT work (no cross-process sharing)

Why This Matters:

  • Queue workers run in separate processes from your web server
  • Progress updates must be shared between these processes
  • Without proper cache driver, progress bars won't update
  • AI fixes may waste tokens if jobs run unexpectedly

Step 4: Configure Queue & Cache (Required for Fix All Features)

⚠️ Important: CodeSnoutr is designed for local development environments only. Do not use in production.

🎯 Quick Setup for Local Development

For the Fix All Issues feature to work properly, you MUST configure both queue and cache drivers:

📋 Cache Driver Requirements

The Fix All progress tracking requires a cache driver that persists across processes:

Driver Status Setup Use Case
file ✅ Recommended Works out of box Local development
database ✅ Supported Run php artisan cache:table Alternative option
array ❌ Won't Work N/A Queue workers can't share data

Why This Matters:

🔧 Queue Worker for Development

Open a new terminal window and run:

Tips:

🛡️ Queue Worker Protection

CodeSnoutr includes automatic queue worker detection to prevent wasting AI tokens:

What You'll See:

📊 Monitoring Progress

The Fix All feature includes comprehensive logging:

Browser Console (F12):

Laravel Logs:

Troubleshooting:

Step 5: Access the Dashboard

Navigate to the CodeSnoutr dashboard:

You should see:

Troubleshooting Installation

Permission Issues

Database Issues

Asset Publishing Issues

Queue Worker Issues

Important: CodeSnoutr now includes queue worker protection to prevent wasting AI tokens. If you try to run Fix All without a queue worker running, you'll see an error message and the job will not be dispatched.

Why This Matters:

See QUEUE_WORKER_PROTECTION.md for detailed documentation.

Manual Installation (Advanced)

If you prefer manual installation or need custom configuration:

1. Publish Components Individually

2. Run Migrations Manually

3. Configure Custom Routes (Optional)

If you want to customize routes, add to your routes/web.php:

Updating CodeSnoutr

When updating to a new version:

Uninstallation

To completely remove CodeSnoutr:

Docker Installation

For Docker environments, add to your Dockerfile:

Production Deployment

For production environments:

  1. Optimize Performance:

  2. Set Up Monitoring:

  3. Configure Logging:

  4. Set Up Scheduled Tasks (Optional):

⚡ Quick Start

🚀 First Scan in 30 Seconds

After installation, get your first scan results immediately:

🌐 Web Interface Walkthrough

  1. Open the Dashboard: Visit http://your-app.com/codesnoutr

  2. Start Your First Scan:

    • Click "New Scan" or "Scan Wizard"
    • Choose scan type: File, Directory, or Full Codebase
    • Select categories: Security, Performance, Quality, Laravel
    • Click "Start Scan"
  3. View Results:

    • Real-time progress updates during scanning
    • Automatic redirect to results when complete
    • Filter by severity: Critical, High, Medium, Low, Info
    • Expand issue groups for detailed analysis
  4. Explore Features:
    • Dark Mode: Toggle in the top navigation
    • AI Assistant: Click the floating AI button (with OpenAI configured)
    • Export: Download results as JSON or CSV
    • Settings: Configure scanning preferences

🛠️ Common Use Cases

Security Audit

Performance Review

Code Quality Check

Pre-deployment Scan

Web Dashboard

Access your CodeSnoutr dashboard:

The web interface provides:

🔄 Enhanced User Experience

CodeSnoutr provides a seamless scanning experience with modern UI/UX features:

🔄 Automatic Queue Management

CodeSnoutr intelligently manages Laravel queues for optimal performance:

No Configuration Required: Queue management works out-of-the-box with sensible defaults. Customize behavior in config/codesnoutr.php if needed.

🤖 AI Smart Assistant

The AI Assistant provides intelligent help throughout your code scanning experience:

Access the AI Assistant: Look for the floating AI button in the bottom-right corner of the interface, or navigate to any CodeSnoutr page where it's available as a slide-out panel.

Configuration: Set up your OpenAI API key in Settings → AI Integration to unlock the full potential of AI-powered assistance.

Artisan Commands

Scan entire codebase:

Scan specific file:

Scan directory:

Filter by categories:

Export results:

⚙️ Configuration

The configuration file is published to config/codesnoutr.php with comprehensive options:

🔍 Scanning Categories

Security 🔒

Implemented Detection Rules:

Performance ⚡

Implemented Analysis Rules:

Code Quality 📝

Implemented Quality Checks:

Laravel Best Practices 🎯

Implemented Laravel Rules:

Blade Template Analysis 🎨

Comprehensive Blade Template Scanning:

🤖 AI Integration (Ready for Implementation)

Current Status

The package includes complete infrastructure for AI integration:

Setup OpenAI (When Ready)

  1. Get an API key from OpenAI
  2. Configure in your .env:

  3. Or configure via the web interface at /codesnoutr/settings

Planned AI Features

🤖 AI Auto-Fix Setup Guide

⚠️ Local Development Only: This package is designed for local development environments.

Prerequisites Checklist

Before using AI Auto-Fix, ensure you have:

Quick Setup

1. Start Queue Worker

Open a new terminal and run:

2. Configure Cache Driver

In your .env:

Or use database cache:

3. Set Up OpenAI API Key

Get your API key from platform.openai.com/api-keys

Option 1: Configure in .env:

Option 2: Use Web Interface:

4. Verify Everything Works

Using AI Auto-Fix

Single Issue Fix

  1. Navigate to scan results
  2. Click on an issue to expand details
  3. Click "AI Auto-Fix" button
  4. Review the proposed fix in the preview
  5. Click "Apply Fix" to implement

Fix All Issues

  1. Navigate to scan results
  2. Click "Fix All with AI" button
  3. Confirm you want to proceed
  4. Monitor progress in real-time:

    • Progress bar shows completion
    • Live updates every second
    • Success/failure count
    • Estimated time remaining
  5. Review summary when complete:
    • Fixed issues count
    • Failed issues count
    • Total cost (AI tokens used)
    • Link to detailed results

Troubleshooting AI Auto-Fix

Common Issues

"Queue Worker Not Running" Error:

Progress Bar Not Updating:

OpenAI Errors:

Cost Management:

Best Practices

  1. ✅ Test Small First: Try a few issues before Fix All
  2. ✅ Review Fixes: Always review AI changes before committing
  3. ✅ Use Git: Commit your code before running auto-fix
  4. ✅ Monitor Costs: Track OpenAI usage and set budget alerts
  5. ✅ Backup Code: Always have backups before automated fixes
  6. ⚠️ Code Privacy: AI sends your code to OpenAI servers
  7. 🔒 Protect Keys: Never commit API keys to version control

📈 Current Status

✅ Production Ready (v1.0.0)

Core Package - 100% Complete

Web Interface - 100% Complete

Developer Experience - 100% Complete

� Ready for Implementation

AI Integration - Infrastructure Complete

Advanced Features - Framework Ready

📊 Package Statistics

�️ Roadmap

OpenAI API Client Implementation

For detailed information about our AI integration plans, see the OpenAI Client Roadmap.

Quick Overview:

📅 v1.1.0 (Q4 2025) - Stability Release

📅 v1.2.0 (Q1 2026) - Performance Release

📅 v1.3.0 (Q2 2026) - Advanced Features

📅 v2.0.0 (Q3 2026) - Intelligence Release

📅 v2.1.0 (Q4 2026) - Expansion Release

📅 v3.0.0 (2027) - Multi-Provider Release

Current Focus:

See OPENAI_CLIENT_ROADMAP.md for complete details including:

�📁 Package Structure

🤝 Contributing

We welcome contributions! Please see CONTRIBUTING.md for details.

Development Setup

  1. Clone the repository

  2. Install dependencies

  3. Set up a test Laravel application

  4. Link the package for development

  5. Run tests and quality checks

Development Tools

The package includes professional development tools:

🔒 Security

If you discover any security-related issues, please email [email protected] instead of using the issue tracker. All security vulnerabilities will be promptly addressed.

Security Features

The package itself includes:

📄 License

The MIT License (MIT). Please see License File for more information.

👥 Credits

📝 Changelog

Please see CHANGELOG for more information on what has changed recently.


🚀 Roadmap

Phase 2: AI Integration (Q4 2025)

Phase 3: Advanced Features (Q1 2026)

Phase 4: Enterprise Features (Q2 2026)


🤝 Contributing

We welcome contributions! CodeSnoutr is open source and available on GitHub.

📍 Repository

🛠️ Development Setup

  1. Clone the repository:

  2. Install dependencies:

  3. Run the test suite:

  4. Format code:

  5. Run static analysis:

📝 Contributing Guidelines

🐛 Bug Reports

When reporting bugs, please include:

💡 Feature Requests

We're always interested in new ideas! Please check existing issues first, then create a new issue with:


📄 License

CodeSnoutr is open-sourced software licensed under the MIT license.


🏆 Why Choose CodeSnoutr?

✅ Production Ready

⚡ Performance Optimized

🎨 Modern Experience

🔧 Developer Friendly


Built with ❤️ for the Laravel community

CodeSnoutr v1.0.0 - Production ready as of August 2025


❓ Frequently Asked Questions

General Questions

Q: Is CodeSnoutr ready for production use? A: Yes! CodeSnoutr v1.0.0 is production-ready with comprehensive testing, professional code quality, and full Laravel compatibility.

Q: What Laravel versions are supported? A: CodeSnoutr supports Laravel 10.0, 11.0, and 12.0 with PHP 8.1+.

Q: Does CodeSnoutr slow down my application? A: No. CodeSnoutr runs scans in background queues and doesn't affect your application's performance. The web interface is lightweight and optimized.

Installation & Setup

Q: Do I need to set up queues? A: While optional, queues are highly recommended for better performance. CodeSnoutr can auto-manage queue workers or you can set up dedicated workers.

Q: Can I customize which files are scanned? A: Yes! Configure scan paths, exclusions, and file types in config/codesnoutr.php or through the web interface.

Q: How do I update CodeSnoutr? A: Run composer update rafaelogic/codesnoutr and republish assets with php artisan vendor:publish --tag=codesnoutr-assets --force.

Features & Functionality

Q: What types of issues can CodeSnoutr detect? A: CodeSnoutr detects 50+ types of issues including security vulnerabilities, performance problems, code quality issues, and Laravel best practice violations.

Q: Can I export scan results? A: Yes! Export results as JSON, CSV, or store them in your database. Use the web interface or CLI commands.

Q: Is AI integration required? A: No. AI features are optional and require an OpenAI API key. All core functionality works without AI integration.

Technical Questions

Q: Can I create custom scanning rules? A: Yes! Extend the AbstractRuleEngine class to create custom rules. See the source code examples in src/Scanners/Rules/.

Q: Does CodeSnoutr work with Docker? A: Yes! CodeSnoutr is fully compatible with Docker. See the installation guide for Docker-specific instructions.

Q: Can I integrate CodeSnoutr with CI/CD? A: Absolutely! Use the CLI commands in your CI/CD pipeline to automatically scan code and fail builds on critical issues.

Troubleshooting

Q: Scans are not starting or taking too long A: Check your queue configuration. Ensure queue workers are running or enable auto-start in the configuration.

Q: Getting permission errors A: Make sure your web server has read permissions on your codebase and write permissions on storage directories.

Q: Web interface not loading properly A: Clear Laravel caches (php artisan cache:clear) and ensure assets are published (php artisan vendor:publish --tag=codesnoutr-assets --force).

Q: UI appears broken with no CSS styling A: This means the assets weren't published correctly. Run:

Verify assets exist at public/vendor/codesnoutr/build/. See CSS_TROUBLESHOOTING.md for detailed help.


🆘 Support & Community

Getting Help

Community

Feature Requests

We're always looking to improve! Submit feature requests through:



All versions of codesnoutr with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
illuminate/support Version ^10.0|^11.0|^12.0
illuminate/console Version ^10.0|^11.0|^12.0
illuminate/database Version ^10.0|^11.0|^12.0
livewire/livewire Version ^3.6.4
nikic/php-parser Version ^4.0|^5.0
symfony/finder Version ^6.0|^7.0
seld/jsonlint Version ^1.11
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 rafaelogic/codesnoutr contains the following files

Loading the files please wait ...