- Is andreyco/instagram a Laravel package?
- No. It is a single, self-contained PHP class that wraps Instagram's legacy REST API and ships with no service provider, facade, config file, migrations, or container binding. In a Laravel application it behaves like any plain Composer library: you instantiate it manually with your credentials and wrap it in your own service class if you want dependency injection. Treat it as a greenfield adapter, not an install-and-configure package.
- Does andreyco/instagram still work with the current Instagram API?
- No. The class targets the pre-2018 Instagram Platform API (v1), which was superseded by the Instagram Graph API and Basic Display API served from graph.instagram.com and graph.facebook.com. Endpoint shapes, authentication, pagination, rate-limit signalling, and error envelopes all differ, so expect 400 or 404 responses rather than soft deprecation warnings. Any spike that appears to succeed is succeeding against your own mocks.
- How do I install andreyco/instagram in a Laravel app?
- Install it with Composer using composer require andreyco/instagram, then instantiate the class directly in a service or controller and pass your credentials. There is no package auto-discovery, no publishable config, and no facade, so you are responsible for wiring credentials, caching, and error handling yourself. The integration effort itself is low, but making it work against a live Meta API is a much larger and likely unbounded task.
- What PHP and Laravel versions does andreyco/instagram support?
- The last release was December 2017, which predates modern PHP 7.2+ typing norms and the Laravel versions in use today. The code may rely on deprecated constructs, direct curl_* calls, and possibly non-PSR-4 autoloading, and it makes no claims about supported PHP or Laravel versions. Run it against your current runtime before estimating any work, and assume you own compatibility going forward.
- What should I use instead of andreyco/instagram for Instagram in Laravel?
- Use the supported Meta APIs instead: the Instagram Graph API for owned business accounts or the Basic Display API for consumer login. In Laravel you can call these directly with Illuminate\Support\Facades\Http, or adopt a maintained Meta SDK if you need more coverage. Both give you proper token models, pagination, and rate-limit handling that a 2017-era client cannot provide.
- Can I fork and modify andreyco/instagram for my own use?
- Yes. The package uses the BSD-2-Clause licence, which permits commercial modification and redistribution provided you keep the attribution. Because the class is small and has almost no dependencies, a fork-and-repoint is technically plausible. Budget a spike first to separate what is genuinely reusable, such as HTTP plumbing and JSON parsing, from what must be rewritten, such as authentication, endpoints, and field selection.
- Is andreyco/instagram maintained and safe for production?
- It is effectively abandoned: last release December 2017, around 80 stars, zero dependents, and no maintainer activity. There is no security patching, no PHP version support policy, and no Meta API version pinning. Using it in production means accepting functional and maintenance risk indefinitely, with a named owner and a documented upgrade path off the fork.
- How should I handle authentication and token storage with andreyco/instagram?
- The class performs an OAuth token exchange and builds requests, but it has no notion of short-lived versus long-lived tokens or app-scoped versus user tokens as Meta defines them today. Token storage, refresh, revocation, and caching of user media are your responsibility and are governed by Instagram and Meta platform terms. A 2017-era client does not help you meet app review or data handling obligations, so plan for that explicitly.
- Does andreyco/instagram carry supply-chain risk?
- Supply-chain risk is low because the dependency surface is near zero and there is no transitive tree to compromise. Forking and vendoring the code is therefore safe from a third-party contamination standpoint. The real risk is staleness, not malicious dependencies, and that is a risk you take on permanently once the package is vendored.
- How do I test an andreyco/instagram integration without a live Instagram API?
- You have to mock the HTTP layer, because the upstream endpoints it targets are retired and will not respond successfully. Write tests against your own adapter or service wrapper rather than the class itself, so you can swap the transport later. Keep in mind that a passing test suite here only proves your mocks are consistent, not that the integration works against Meta's current APIs.