Download the PHP package parallel-oss/laravel-compliance without Composer

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

Laravel Compliance

Latest Version on Packagist GitHub Tests Action Status GitHub Code Style Action Status Total Downloads

Laravel Compliance lets you map code-level evidence to curated, enum-backed controls and generated technical requirements. It does not claim that an annotation proves compliance; it gives teams a typed, reviewable way to connect implementation evidence to framework requirements, monitoring tests, and audit-friendly reports.

Installation

You can install the package via composer:

You can publish the config file with:

How It Works

Application code is tagged with plain-English behavior controls:

The package then maps that behavior through prepackaged local data:

Package users do not import remote data or generate enums before using the package. The raw source data has already been processed into local seed arrays under resources/frameworks/vanta/data:

These files are plain PHP arrays so downstream applications can seed their own database:

The public ComplianceControl enum is intentionally curated. It includes engineering-relevant behaviors for access, encryption, logging, monitoring, SDLC, vulnerability management, privacy engineering, vendors, and related security operations. It excludes policy-only, HR-only, physical-office, board, insurance, meeting-minute, and pure audit-placeholder controls from code-facing evidence.

LLM Agent Skills

This package publishes portable Agent Skills under skills/ and advertises them through Composer metadata:

Agents that support Composer-discovered skills can sync them from the package. Agents that read repository instruction files can use AGENTS.md.

For Cursor projects, publish the packaged skills into the current project:

This writes Cursor project skills to .cursor/skills using Cursor's expected directory format:

Existing project skills are not overwritten unless you pass --force.

Usage

Prefer control evidence when the code demonstrates behavior that may support multiple frameworks:

Use gap markers when the code path should have compliance-related behavior but does not yet. These markers do not appear in the evidence report and should not be treated as implemented controls:

Control metadata and framework mappings are loaded from prepackaged local seed arrays. The enum stays small and ergonomic; source IDs, titles, descriptions, domains, framework controls, and related monitoring tests are implementation details that the report expands automatically.

You may still use direct requirement enums when your application already owns a technical requirement catalog:

The legacy Parallel\Compliance\Compliance attribute remains available as an alias, but new code should use Evidence.

Generate Reports

Generate a Markdown evidence report:

Generate a Markdown gap report for missing compliance work:

Useful options:

Testing

Changelog

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

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

License

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


All versions of laravel-compliance with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
illuminate/contracts Version ^11.0 || ^12.0 || ^13.0
nikic/php-parser Version ^5.7
spatie/laravel-package-tools Version ^1.93
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 parallel-oss/laravel-compliance contains the following files

Loading the files please wait ...