Is 3rdpartyeve/phealng compatible with Laravel?

PhealNG is not a Laravel package. It is a framework-agnostic legacy PHP library with no service provider, facade, configuration integration, or Laravel HTTP-client abstraction. Adding it to Laravel would create an isolated legacy dependency rather than a native application component.

Can I install PhealNG with Composer in a Laravel application?

It is technically installable via Composer, but it provides little practical value because the upstream EVE XML API was shut down in 2018. Its PHP 5.4-era baseline and PSR-0 design are likely to conflict with modern Laravel versions that require PHP 8.x and maintained dependencies. Avoid adding it unless you are preserving an existing legacy integration.

Why is PhealNG deprecated and archived?

CCP ended the EVE Online XML API in 2018, so the library no longer has a working upstream integration target. The repository is archived and the README explicitly says the library is probably not what you are looking for. It receives no maintenance, bug fixes, or security patches.

Does PhealNG still work with the EVE Online API?

No. PhealNG was built for the retired EVE Online XML API, which CCP shut down in 2018. Any calls to live endpoints should fail or be meaningless, so it is not suitable for production integrations. Remaining uses are limited to historical code retention or local mocks.

What should I use instead of PhealNG for EVE Online API access?

Use EVE ESI, CCP's current API, through a maintained ESI client or a thin internal HTTP client built on Laravel's HTTP client or Guzzle. Inventory the features that depended on the old XML API and map them to ESI endpoints or remove obsolete functionality. Treat migration as removal of PhealNG rather than adoption of another legacy XML API wrapper.

What PHP and Laravel versions does PhealNG support?

PhealNG requires PHP 5.4 or newer and follows PSR-0-era classloading, with no declared support for modern Laravel versions. Its archived status and old dependency baseline make it a likely blocker for Laravel 9, 10, or 11 environments running PHP 8.x. Verify Composer constraints before any temporary install, and expect manual wiring rather than package auto-discovery.

How do I remove PhealNG from a legacy Laravel application?

Start by inventorying every reference and confirming whether any endpoint still functions. Freeze new development against the package, wrap remaining calls behind an application-owned adapter or service interface, then replace functionality with EVE ESI or remove it. Use a feature flag during transition, remove the Composer dependency and legacy configuration, and add regression tests and monitoring to confirm no calls remain.

Is PhealNG maintained or secure for production use?

No. The repository is archived and explicitly deprecated, with no upstream maintenance, security patching, or active dependents. The core integration target no longer exists, so retaining it creates unmaintained dependency risk and upgrade blockers. Production use would also provide false confidence that an obsolete integration can be supported.

Can I use PhealNG for historical EVE data or testing?

PhealNG should not be used for live EVE API access because the XML API is gone. It might only be relevant for retaining historical code paths or using local mocks and fixtures in legacy tests. Even then, isolate it from shared application dependencies and plan to remove it.

What are the alternatives to PhealNG for Laravel developers?

For current EVE Online integrations, use EVE ESI with a maintained ESI client or Laravel's HTTP client. For obsolete features, remove them rather than replacing PhealNG with another retired XML API library. If legacy retention is mandatory, keep PhealNG behind an internal adapter and migrate away as soon as possible.

Weave Code

Weaver

Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.

Phealng Laravel Package

3rdpartyeve/phealng

PhealNG is a PHP client library for the EVE Online XML API, offering namespaced, PSR-0 compatible classes. Note: this package is deprecated and archived, since CCP shut down the XML API in 2018, so it is not suitable for new projects.

View on GitHub

Deep Wiki

Context7

ARCHIVED This used to be the most used API library for the game EVE Online, before the API was replaced in 2018

Frequently asked questions about Phealng

Is 3rdpartyeve/phealng compatible with Laravel?: PhealNG is not a Laravel package. It is a framework-agnostic legacy PHP library with no service provider, facade, configuration integration, or Laravel HTTP-client abstraction. Adding it to Laravel would create an isolated legacy dependency rather than a native application component.
Can I install PhealNG with Composer in a Laravel application?: It is technically installable via Composer, but it provides little practical value because the upstream EVE XML API was shut down in 2018. Its PHP 5.4-era baseline and PSR-0 design are likely to conflict with modern Laravel versions that require PHP 8.x and maintained dependencies. Avoid adding it unless you are preserving an existing legacy integration.
Why is PhealNG deprecated and archived?: CCP ended the EVE Online XML API in 2018, so the library no longer has a working upstream integration target. The repository is archived and the README explicitly says the library is probably not what you are looking for. It receives no maintenance, bug fixes, or security patches.
Does PhealNG still work with the EVE Online API?: No. PhealNG was built for the retired EVE Online XML API, which CCP shut down in 2018. Any calls to live endpoints should fail or be meaningless, so it is not suitable for production integrations. Remaining uses are limited to historical code retention or local mocks.
What should I use instead of PhealNG for EVE Online API access?: Use EVE ESI, CCP's current API, through a maintained ESI client or a thin internal HTTP client built on Laravel's HTTP client or Guzzle. Inventory the features that depended on the old XML API and map them to ESI endpoints or remove obsolete functionality. Treat migration as removal of PhealNG rather than adoption of another legacy XML API wrapper.
What PHP and Laravel versions does PhealNG support?: PhealNG requires PHP 5.4 or newer and follows PSR-0-era classloading, with no declared support for modern Laravel versions. Its archived status and old dependency baseline make it a likely blocker for Laravel 9, 10, or 11 environments running PHP 8.x. Verify Composer constraints before any temporary install, and expect manual wiring rather than package auto-discovery.
How do I remove PhealNG from a legacy Laravel application?: Start by inventorying every reference and confirming whether any endpoint still functions. Freeze new development against the package, wrap remaining calls behind an application-owned adapter or service interface, then replace functionality with EVE ESI or remove it. Use a feature flag during transition, remove the Composer dependency and legacy configuration, and add regression tests and monitoring to confirm no calls remain.
Is PhealNG maintained or secure for production use?: No. The repository is archived and explicitly deprecated, with no upstream maintenance, security patching, or active dependents. The core integration target no longer exists, so retaining it creates unmaintained dependency risk and upgrade blockers. Production use would also provide false confidence that an obsolete integration can be supported.
Can I use PhealNG for historical EVE data or testing?: PhealNG should not be used for live EVE API access because the XML API is gone. It might only be relevant for retaining historical code paths or using local mocks and fixtures in legacy tests. Even then, isolate it from shared application dependencies and plan to remove it.
What are the alternatives to PhealNG for Laravel developers?: For current EVE Online integrations, use EVE ESI with a maintained ESI client or Laravel's HTTP client. For obsolete features, remove them rather than replacing PhealNG with another retired XML API library. If legacy retention is mandatory, keep PhealNG behind an internal adapter and migrate away as soon as possible.

Popularity trends

Recorded values over time (once-a-day snapshots). Oct 9, 2026 – Nov 7, 2026

GitHub · stars

GitHub · forks

GitHub · watchers

Packagist · monthly downloads

View on GitHub

Stars

Favorites

Forks

Score

0.4

Score breakdown

Sum of components, capped 0–100. Halved if archived.

Stars

input: 66

+0.3
Forks

input: 15

+0.4
Open issues + PRs

input: 0

+0.0
Releases

input: 0

+0.0
Recency

input: —

+0.0
Issue opportunity

input: 0

+0.0
Laravel News mentions

input: 0

+0.0
Dependents

input: 0

+0.0

Archived: total halved

Total 0.4

Opportunity

1.2

Opportunity score breakdown

Hidden gem signal × 0.65 + contribution need × 0.35, scaled by health factor.

Hidden gem

log(monthly_downloads / (stars + 1)) × 25

3.1
Contribution need

open_issues + open_prs: 0

0.0
Health factor

archived + recency + open issues

×0.60

Total 1.2

License

MIT

Watchers

Downloads

22/mo

Dependents

Open issues

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.

Add packages to context

No packages found.

jinas/dhivatar

store-doc/laravel-storage-driver

plus-it/laravel-translation-manager

diephp/perhaps

diephp/telegraph

osmaviation/spreadsheet

microsoft/fluentui-system-icons

mmccook/php-json-canonicalization-scheme

middlewares/firewall

qubiqx/montapacking

nyoncode/laravel-package-console

pnscripts/filament-broadquill-lite

pnscripts/laravel-sentfold-lite

vleap/mx-sdk-laravel-internal

twidpay/utils

htetmyathlaing/scout-elasticsearch-driver

artisan-toolbox/front-awesome

ls/client-assistant

users-au/laravel-client

cgv/localized-resource