- Does sseffa/video-api support Laravel 9, 10, or 11?
- Unlikely without changes. The package's last release was in 2017, so PHP 8+ and Laravel 9/10/11 compatibility is not expected out of the box. Run composer why-not against your target versions and plan to fork or override dependencies if you need it.
- How do I install sseffa/video-api with Composer?
- Install it with composer require sseffa/video-api in a Laravel application. Because of the old release, expect dependency constraints to conflict with modern Laravel and PHP versions. A short sandbox install is the fastest way to confirm whether Composer will resolve it.
- Does this package call the official YouTube Data API v3 and Vimeo API?
- The evaluation recommends verifying this in a sandbox spike. It is unclear whether the package wraps official YouTube Data API v3 and Vimeo APIs or mainly parses video URLs. Do not assume full API client behavior until you inspect the source.
- Is sseffa/video-api maintained and safe for production?
- Treat it as high risk for production. The package is stale, upstream maintenance is effectively absent, and external video APIs have changed since 2017. If you adopt it, fork and pin it, wrap it in an internal adapter, and assign an owner.
- What video data does sseffa/video-api return?
- The exact data contract should be confirmed by inspecting the source and testing responses. The package is intended for video-related metadata, but the evaluation warns about possible silent response-mapping errors. Contract tests around your internal adapter are recommended.
- How do I configure YouTube and Vimeo API credentials?
- Credential configuration likely depends on Laravel config files and the package's service provider, but this needs confirmation in the code. The evaluation flags credential handling gaps as a risk. Keep keys in environment variables and rotate them through your own operations runbook.
- Does the package handle API quotas, rate limits, retries, and caching?
- The evaluation says these concerns are not clearly covered and should be added by your application. Implement caching, rate limiting, retries, circuit breakers, and observability around the package. Avoid synchronous video API calls on user-facing request paths.
- Are there tests for sseffa/video-api?
- The evaluation lists tests as a key question, which suggests coverage is uncertain or minimal. Check the repository before relying on it. If you fork, add contract tests against your VideoMetadataProvider interface.
- What alternatives should I consider for YouTube and Vimeo metadata in Laravel?
- Prefer a thin first-party client using Laravel's HTTP client, cache, and queue primitives if the package does not install cleanly. The evaluation also suggests using the package as a reference implementation. This gives you control over quota, retries, and API changes.
- Can I fork sseffa/video-api or extract its logic into my own adapter?
- Yes. MIT licensing makes forking feasible, and the evaluation recommends a private fork with explicit version constraints. Wrap the fork in an internal VideoMetadataProvider-style interface so controllers and jobs do not depend on package classes directly.