- How do I install graham-campbell/packagist-stats?
- Install it with Composer, for example as a development or global dependency in a Laravel or PHP project. After installation, run the provided CLI command from your terminal. Check the repository README for the exact binary name and current Composer constraints before adding it to automated workflows.
- Does graham-campbell/packagist-stats work with Laravel?
- It is a framework-agnostic CLI tool, so it does not require Laravel integration to run. Laravel teams can install it as a Composer dependency or globally and use it alongside existing developer tooling. No Laravel service provider or runtime integration is documented, so treat it as a command-line utility rather than an application package.
- How do I display download stats for a Packagist package?
- Run the package's CLI command and pass the public Packagist package name you want to inspect. The tool retrieves Packagist statistics and displays download counts in human-readable output. Use the command help output to confirm the current argument and option syntax.
- Can I get JSON or machine-readable output from this tool?
- Machine-readable output is not documented in the available context, and the tool appears intended for human-readable CLI reports. If you need JSON for automation, calling the Packagist API directly or wrapping the CLI output carefully is safer. Avoid depending on parsed CLI text as a stable contract.
- Does it support private Packagist packages or authentication?
- Private-package authentication is not documented, so assume it is best suited to public Packagist packages. For private packages, use the Packagist API with appropriate credentials or maintain an internal script. Do not put credential-dependent reporting into a workflow until you have verified support.
- Which PHP and Composer versions does graham-campbell/packagist-stats support?
- The supported PHP and Composer versions are defined by the package's composer.json constraints and README, not by a Laravel version. Validate those constraints against your team's PHP matrix before installing it in CI. Because it is framework-agnostic, Laravel version support is not the main compatibility concern.
- Can I run graham-campbell/packagist-stats in CI or a scheduled job?
- Yes, it can be invoked locally, in CI, or from cron because it is a CLI utility with a low blast radius. Pin the package version, ensure network egress to Packagist is allowed, and add timeouts plus non-zero exit handling. Do not place it in a release-blocking path unless the report is business-critical.
- What are the Packagist API rate limits and retry behavior for this tool?
- The tool depends on Packagist, so Packagist API rate limits and availability can affect runs. The available context does not document built-in retry or backoff semantics, so wrap scheduled invocations with your own retry policy. Cache results and avoid polling more often than your reporting needs require.
- Is graham-campbell/packagist-stats actively maintained?
- Active maintenance is not confirmed by the available context, and low adoption signals such as zero stars and dependents suggest maturity risk. Check the GitHub repository for recent releases, issues, and commit activity before standardizing on it. Pin the version and plan to fork or replace the tool if it becomes unmaintained.
- What are alternatives to this CLI for Packagist download statistics?
- You can call the Packagist API directly from a small internal script or custom Laravel Artisan command. Other package analytics and dependency-governance tools may also provide download reporting. Keep the CLI invocation behind a Make target or wrapper so you can swap implementations without changing team workflows.