- Is wolfcode/qiniu-php-sdk a Laravel package?
- No. It is a low-level PHP SDK for Qiniu REST services, not a Laravel integration. It does not ship a service provider, publishable config, facade, or Flysystem adapter. In Laravel you must bind it in your own service provider or wrap it behind an interface before using it.
- How do I install and configure wolfcode/qiniu-php-sdk in a Laravel app?
- Install it with Composer using composer require wolfcode/qiniu-php-sdk. Then construct the Qiniu clients, such as Auth, UploadManager, and StorageManager, with your AccessKey, SecretKey, bucket, and domain. In Laravel, keep those credentials in config/services.php or environment variables and resolve the clients from the container. Do not commit secrets or hard-code them in controllers.
- Does wolfcode/qiniu-php-sdk support Laravel 11, Laravel 12, PHP 8.2, and PHP 8.3?
- The package is not Laravel-specific, so Laravel version support is not declared by the package itself. The technical assessment flags PHP and Guzzle constraints as unverified for Laravel 11 and 12 on PHP 8.2 and 8.3. Check composer.json in the repository and test an install in a scratch Laravel app on your exact PHP version before assuming compatibility.
- Is wolfcode/qiniu-php-sdk safe and trusted for production use?
- Treat it as high risk until you audit it. The assessment notes 0 stars, 0 dependents, and a publisher that is not the official Qiniu vendor. Because it signs upload tokens and private URLs with your AccessKey and SecretKey, source review and version pinning are mandatory. The unexplained jump from 0.1.2 to 8.0.1 with no changelog body is a process warning, not a neutral detail.
- Why did wolfcode/qiniu-php-sdk jump from version 0.1.2 to 8.0.1, and what changed?
- The context says the jump likely re-baselines the package to track an upstream major line, but the release notes disclose nothing. That means there may be many prior breaking releases you never reviewed, and the exact API signatures are unknown until diffed. Diff v0.1.2 against v8.0.1, then compare v8.0.1 with the matching upstream qiniu/php-sdk tag before trusting any call shape.
- Can wolfcode/qiniu-php-sdk conflict with the official qiniu/php-sdk if both are installed?
- It can, and this is a concrete Composer risk. If the package declares replace for qiniu/php-sdk at 8.0.1 while a transitive dependency requires qiniu/php-sdk ^7.0, Composer may install the official package alongside it. That can produce duplicate Qiniu classes and a fatal redeclare. Test this with a deliberate transitive dependency in a scratch project and inspect the replace and provide constraints, not just their presence.
- Does wolfcode/qiniu-php-sdk support token v2, multipart uploads over 4 MB, private buckets, and QBox callback authorization?
- The intended surface includes Auth token generation, UploadManager putFile, StorageManager operations, private download URLs, and CDN refresh. However, the assessment marks token v2, multipart uploads over 4 MB, private-bucket signing, and QBox callback Authorization handling as unverified. Validate each of those flows against the installed version in a staging bucket. Do not assume the 0.1.x signatures still apply in 8.0.1.
- Can I use wolfcode/qiniu-php-sdk with Laravel Storage::disk() or Flysystem?
- Not out of the box. It is not a Flysystem adapter, so it does not plug into Storage::disk() or Storage::temporaryUrl() by itself. You can wrap it in a custom Flysystem adapter or behind a QiniuStorage interface and facade so application code uses Laravel's storage abstraction. That confines Qiniu-specific code and vendor lock-in to one class.
- How should I test wolfcode/qiniu-php-sdk before adopting it?
- Create a scratch Laravel app on your target PHP version and install a fixed package version. Write tests for upload-token signing, private URL expiry, uploads larger than 4 MB, callback authorization, and region resolution. Also test dependency resolution with a package that requires the official qiniu/php-sdk. Run staging checks with a separate bucket and short-lived credentials before any production rollout.
- What alternatives to wolfcode/qiniu-php-sdk should I consider for a Laravel project?
- The official qiniu/php-sdk is the baseline for Qiniu API coverage and avoids the publisher and version-lineage concerns here. If you want Laravel's Storage abstraction, use or build a maintained Flysystem adapter and keep it behind your own interface. Choose wolfcode/qiniu-php-sdk only if you can audit the diff, pin the version, and accept the documented production risks.