Weave Code
Commit History Laravel Package
spiriitlabs/commit-history
Laravel package that brings Git commit history into your application, with a simple built-in interface to browse recent commits, inspect changes, and keep project history accessible to your team without leaving the admin area.
Fetch git commit history.
Frequently asked questions about Commit History
- What is spiriitlabs/commit-history used for?
- It is a Laravel package that fetches Git commit history from GitHub or GitLab and provides a built-in admin interface for browsing recent commits and inspecting changes. It is intended to keep project history accessible to your team without leaving your application's admin area. Architecturally it works as a thin infrastructure adapter around the provider REST APIs rather than a domain-layer dependency.
- How do I install spiriitlabs/commit-history in a Laravel app?
- Install it with Composer using composer require spiriitlabs/commit-history. If the package ships a publishable config file and service provider, publish the config and set your provider credentials as described in the package source. Because the project has little public documentation, verify the service provider registration and config keys directly in the repository before wiring it into your application.
- Does the package support both GitHub and GitLab?
- Yes, the package is described as wrapping the GitHub and GitLab REST APIs to retrieve commit history and return a normalized result set. That normalization is important because it keeps provider-specific vocabulary out of your callers. Confirm the normalized commit model in the source, since the exact fields exposed are not documented in the provided context.
- Which Laravel and PHP versions does spiriitlabs/commit-history support?
- The package is described as suitable for Laravel 9, 10, 11, and 12 applications on PHP 8.1 or newer. However, you should verify the declared php and illuminate/support constraints in composer.json before installing, because the package is new and unvetted. Running composer why-not or checking the lock file will quickly confirm compatibility with your application.
- How do I authenticate with GitHub or GitLab when using this package?
- You will need to provide a credential such as a personal access token for the provider you want to query. The technical evaluation flags that the exact supported auth modes, whether PAT, OAuth, or GitHub App installation tokens, must be verified against the source. Store tokens in your Laravel environment or secrets manager and confirm the package never logs tokens or full request URLs.
- Can I use spiriitlabs/commit-history with self-hosted GitLab or GitHub Enterprise?
- Self-hosted support depends on whether the package exposes configurable base URLs for enterprise or self-managed instances. The technical evaluation lists this as an open question rather than a confirmed feature. Inspect the configuration options and HTTP client setup in the source before assuming your enterprise host will work.
- How does the package handle pagination and API rate limits?
- Pagination and rate-limit behavior are not documented in the provided context, so you should not assume full history traversal or automatic backoff. The technical evaluation specifically asks whether the package exposes cursors, silently defaults to page one, and surfaces or retries 429 and 403 secondary-limit responses. Test these paths against both providers before relying on the package in production.
- Is spiriitlabs/commit-history safe to use in production?
- Treat it as unvetted code: the repository has zero stars and zero dependents, and there is no community-corroborated integration path or issue backlog to mine for known failures. The main risks are external API drift, credential handling, and abandonment by the agency owner. The MIT license and small code volume cap the downside, because the worst case is forking and owning a few hundred lines yourself.
- Can I cache commit history to avoid hitting GitHub or GitLab rate limits?
- The package itself is described as a thin API wrapper, so caching is best added at your application layer using Laravel's Cache facade, queued backfill jobs, and RateLimiter for token-bucket throttling. Conditional requests such as ETag or If-None-Match are not confirmed in the provided context, so verify whether the package supports them before assuming cheap repeat calls. A short cache TTL on commit listings is usually enough to keep admin browsing responsive without exhausting API quotas.
- Who maintains spiriitlabs/commit-history, and what happens if it is abandoned?
- The package is owned by SpiriitLabs, an agency, and the provided context does not identify a named maintainer, support policy, or deprecation policy. With no stars or dependents, there is little external signal that the project will receive timely releases for GitHub or GitLab API changes. If it is abandoned, the MIT license lets you fork the repository and maintain the small codebase internally.
Weaver
How can I help you explore Laravel packages today?