- Can I install renatomarinho/laravel-gitscrum as a Composer package inside my existing Laravel app?
- No. Although it is distributed through Packagist, GitScrum is a complete Laravel monolith with its own auth, teams, notifications, and project/board/backlog/sprint/task domain. It exposes no service provider designed for host-app consumption, no facade over a stable API, and no published extension points, and the zero-dependents count confirms nobody consumes it as a library. Adopting it is a fork-and-operate decision on an entire application, not an integration.
- What Laravel and PHP versions does GitScrum support?
- The last release is dated 2017-10-01, which places the codebase in the Laravel 5.4/5.5 era with PHP 7.0/7.1 constraints. A composer install will not resolve cleanly on PHP 8.2 or 8.3, and the transitive tree including Symfony components, Guzzle, PHPUnit, and Doctrine DBAL is years past end of life. Check the constraint matrix in composer.json before planning anything.
- Is GitScrum still actively maintained?
- Upstream energy has visibly moved to the commercial SaaS offering, leaving the open-source repository as a legacy artifact. There is no published security policy and no maintainer response channel for vulnerability reports. Confirm whether the repository is archived or carries a written statement of intent from the maintainer before committing.
- How do I install and run GitScrum from source?
- You clone the repository and run composer install on a period-appropriate PHP 7.x runtime, since a modern PHP 8 runtime will not resolve the dependency graph. Then configure MySQL, Redis for queue and cache, a queue worker, a cron entrypoint, local or S3-compatible object storage, and outbound SMTP, and rebuild front-end assets with the era-appropriate Node and Webpack toolchain. Budget the asset rebuild as its own workstream.
- What infrastructure does GitScrum need in production?
- Treat the minimum footprint as PHP-FPM, MySQL or MariaDB, Redis for queue and cache, a cron entrypoint, S3-compatible or local object storage, and outbound SMTP. That stack only suits PHP/Laravel shops already operating MySQL and a queue worker. Polyglot or JVM and Node-centric organizations would be adopting an entire runtime just to get a board tool.
- Does GitScrum support SSO, SAML, or OIDC?
- The authentication and authorization model is not documented as supporting enterprise SSO, SAML, or OIDC; expect local accounts plus OAuth for GitHub, GitLab, and Bitbucket repository connections. Verify this directly against the codebase, because it usually decides enterprise viability. If SSO is a hard requirement, treat the absence as a blocker rather than a configuration task.
- What are the security risks of running GitScrum in production today?
- There is no upstream patch process, so every future CVE in the framework, Symfony, Guzzle, and Doctrine dependency tree becomes yours to remediate. The dependency graph itself already carries known advisories because it is years past EOL. If you must run it, isolate it in a network segment and document the explicit acceptance of unpatched dependencies with a hard sunset date.
- Can I upgrade GitScrum to a modern Laravel version?
- Yes, but plan it as a framework-upgrade project, not an integration: a staged move from 5.x to 8 and then 10 or 11, with the domain logic preserved. Expect multiple months with one or two engineers, gated by a test suite or a newly written characterization suite. The front-end asset pipeline needs a parallel modernization workstream.
- Does GitScrum have automated tests I can rely on?
- Test coverage is unknown and there is no CI signal at this age, so refactors have no safety net. Before changing framework or dependency versions, write a characterization suite that pins the backlog, sprint, and task behavior you depend on. That suite becomes the gate for every subsequent upgrade step.
- What are good alternatives to GitScrum, or how do I migrate off it?
- The lowest-risk path is to mine the schema and domain model for backlog and sprint semantics and write your own thin service, which carries no operational burden or security exposure. If you want a ready-made board, evaluate maintained open-source tools such as Taiga, Leantime, Plane, or OpenProject, or buy the GitScrum SaaS. Because your historical velocity and board data would live in a schema you own, confirm a data export path via API, CSV, or stable DB schema before adopting it.