- Is getjump/vk compatible with Laravel 10 and 11?
- No, not out of the box. The package is a framework-agnostic PHP client with no Laravel service provider, and its Composer constraints target PHP 5.x/7.0-era dependencies including older Guzzle versions that conflict with Laravel's guzzlehttp/guzzle ^7. Installing it in a modern Laravel app will likely fail dependency resolution before runtime.
- Does getjump/vk work on PHP 8?
- It is not officially supported. The codebase reflects PHP 5.x/7.0 conventions and has had no release since 2016, so you should expect deprecations and strict-type issues on PHP 8. Running it on PHP 8 would require a fork with compatibility patches and thorough testing.
- How do I install getjump/vk with Composer?
- You can try composer require getjump/vk, but dependency resolution may fail in a modern Laravel project because of PHP and Guzzle version constraints. If you must evaluate it, use an isolated scratch project or a fork with updated constraints rather than adding it to a production Laravel app. The recommended path is to use VK's official SDK or reimplement the few endpoints you need with Laravel's HTTP client.
- Is getjump/vk still maintained?
- No. The upstream repository is marked abandoned and has had no release since October 2016, with zero dependents providing ecosystem pressure for compatibility. There are no security patches, no CVE response, and no updates for newer VK API versions or PHP releases. Treat any use as a permanent fork obligation.
- What VK API version does getjump/vk support?
- The client models VK API v5.x conventions from the 2014–2016 era, with access-token authentication and a configurable API version. It does not natively model modern VK ID OAuth 2.1 flows or newer endpoint namespaces. You must verify every method and response shape against the current VK API before relying on it.
- Can getjump/vk handle VK authentication in Laravel?
- It is a transport client for authenticated VK API calls, not a Laravel auth integration. It expects an access token but does not provide service provider bindings, config publishing, token storage, rotation, or OAuth callback handling. You would need to build the Laravel-facing token and configuration layer yourself.
- How should I test getjump/vk in a Laravel application?
- Do not mock the package directly throughout your code. Wrap it behind a first-party interface such as App\Services\Vk\VkClientContract, bind that in a service provider, and mock the interface in tests. Because the package is not Laravel-aware, this wrapper also isolates you from its HTTP and response-parsing behavior.
- What are the best alternatives to getjump/vk?
- For official coverage, evaluate vkcom/vk-php-sdk from VK. For Laravel projects, the most maintainable option is often a small first-party client built on Laravel's Http facade with typed request and response classes for only the endpoints you need. That avoids the abandoned dependency and gives you control over retries, logging, and token rotation.
- Is getjump/vk safe to use in production?
- It carries significant production risk. The package is abandoned, has unmaintained transitive dependencies, and will not receive security patches or API updates. There are also compliance considerations around sending user data to VK infrastructure that require legal review before production traffic.
- Does getjump/vk support file uploads and common VK workflows?
- Yes, per its documentation it supports file uploads and common VK workflows alongside simple method calls and JSON response handling. However, those workflows were written for the VK API of the mid-2010s. You should validate upload endpoints, error envelopes, and rate-limit behavior against the current API, or reimplement the specific flows you need.