Grumphp License Task Laravel Package

Product Decisions This Supports

• Automated Compliance Enforcement: Integrates seamlessly into GrumPHP workflows to enforce license validity as part of pre-commit or pre-push hooks, reducing legal/compliance risks in open-source or internally shared projects.
• Developer Onboarding Efficiency: Eliminates manual LICENSE file creation/validation, accelerating contributor ramp-up by auto-generating or correcting files during CI checks.
• Consistent Licensing Across Repositories: Standardizes license formats (MIT, LGPL, AGPL, etc.) across all projects, aligning with company open-source policies or FOSS contributions.
• CI/CD Pipeline Optimization: Build vs. Buy Decision: Avoids reinventing the wheel by leveraging this low-maintenance, battle-tested solution (vs. custom scripts or manual checks).
• Roadmap Alignment:
  • Short-term: Mandate license validation in all new PHP/Laravel projects as a default GrumPHP task.
  • Mid-term: Extend to internal codebases where vendor/third-party licensing requires auditing.
  • Long-term: Explore dynamic license updates (e.g., auto-populating holder/year from Git metadata) or custom license templates for proprietary projects.

When to Consider This Package

• Adopt if:

  • Your team uses GrumPHP for static analysis and needs license compliance automation.
  • You maintain open-source projects or require OSI-approved licenses (MIT, LGPL, etc.).
  • You want to reduce manual compliance checks in CI/CD pipelines (e.g., GitHub Actions, GitLab CI).
  • Your developer onboarding suffers from missing/incorrect LICENSE files.

• Look Elsewhere if:

  • You need non-OSI licenses (e.g., proprietary, Apache 2.0 not listed).
  • Your stack doesn’t use GrumPHP (consider standalone tools like ergebnis/license).
  • You require advanced license customization (e.g., dynamic placeholders, multi-file licenses).
  • Your team lacks PHP/Laravel expertise to integrate GrumPHP tasks.

How to Pitch It (Stakeholders)

For Executives: "This package automates license validation in our CI pipelines, ensuring all open-source contributions comply with legal requirements—reducing risk and saving engineering time. For example, it auto-generates or corrects LICENSE files during code reviews, cutting manual compliance checks by 80%. It’s a low-cost, high-impact solution for governance, especially if we’re expanding FOSS contributions or internal code sharing."

For Engineering/DevOps: *"We’re adding a GrumPHP task to validate LICENSE files—it’s like php-cs-fixer but for licenses. It:

• Auto-creates missing LICENSE files (MIT/LGPL/AGPL).
• Fixes errors in existing files (e.g., wrong year/holder).
• Integrates into our CI with zero extra tooling. No more ‘license missing’ blockers in PRs—just one less thing to remember."

For Legal/Compliance: "This tool enforces license consistency across all repositories, aligning with our open-source policy. It’s audit-ready—every commit is checked, and invalid licenses are flagged or auto-fixed. We can even extend it to internal projects where vendor licensing requires scrutiny."