Sde Laravel Package

Product Decisions This Supports

• Feature enablement for EVE Online–adjacent products. The package ingests CCP's Static Data Export (SDE) into a Laravel database and now exposes typed DTOs for solar systems, types, effects, dogma, and flags. This directly underpins roadmap items such as fitting/attribute calculators, route planners, market and industry calculators, wormhole/exploration maps, and corp management dashboards.
• Map and spatial features (new in v0.6.1). Added 2D position fields on solar systems plus corresponding DTO updates lower the cost of building a map view or spatial analytics without bolting on a third-party map API. This is a concrete input to a "build in-house map" vs. "integrate external map service" decision.
• Fitting engine feasibility (new in v0.6.1). New DTOs for type effects and dogma, with nullable-field handling fixed in EffectDto/EffectModifierDto, make attribute/modifier calculation a realistic in-house capability rather than a research spike.
• Build vs. buy for data plumbing. Sourcing, normalizing, and re-seeding the SDE is undifferentiated heavy lifting. Adopting this package is a "borrow" decision that shifts engineering time toward differentiating features.
• Data lifecycle ownership. Fixes for incorrect/phantom Jove systems and an increased SDE download timeout signal that dataset correctness and ingestion reliability are actively maintained — relevant when deciding whether to own data QA internally.
• Quality-bar signal. Strict types and PHPStan level-max fixes indicate a maintainer investing in type safety, which supports adopting DTOs as the internal contract for EVE domain objects.

When to Consider This Package

Consider adoption when:

• You are building an EVE Online tool on Laravel/PHP and need systems, types, dogma/effects, or flags as first-class, typed domain objects.
• You want DTOs over raw arrays for static analysis, refactors, and safer downstream feature work.
• You need bulk seeding commands for a large reference dataset and prefer a maintained ingestion path over a bespoke ETL.
• Your feature set is read-mostly reference data (lookups, calculations, maps) rather than live game state.

Look elsewhere or defer when:

• API stability is required. This is a 0.x release; breaking changes between minor versions are expected. Pin versions and budget upgrade work.
• You need real-time or player-specific data — this is static export data only; ESI integration is a separate concern.
• You are not on Laravel/PHP, or you want a vendor-supported, SLA-backed, documented API with backward-compatibility guarantees.
• You require long-term maintenance assurance; a single-maintainer package with no LTS should be treated as a dependency risk to be wrapped behind your own abstraction layer.
• Licensing/redistribution of CCP's SDE data has not been cleared for your commercial use case.

How to Pitch It (Stakeholders)

For executives: This package removes the most tedious part of building EVE Online features — importing and maintaining CCP's static game data — and the latest release adds map-ready coordinates and the data structures needed for ship fitting and attribute calculations. It shortens time-to-market for data-driven features and lets engineering spend its time on product differentiation instead of data pipelines.

For engineering: Laravel-native ingestion with typed DTOs, strict types, and PHPStan level-max cleanup; seeding commands handle bulk loads, and v0.6.1 adds 2D system positions, effect/dogma DTOs, and flags. Caveats to plan around: it is pre-1.0, so pin versions and isolate it behind an internal adapter; upstream SDE download reliability is a known weak point (hence the timeout increase); and dataset correctness fixes (Jove systems) mean you should validate seeded data rather than assume it.

Risks to acknowledge: single-maintainer dependency, 0.x versioning without compatibility promises, network dependency on CCP's export endpoints, and data licensing terms. Mitigation: wrap the package behind your own repository/DTO boundary so it can be swapped, and add a smoke test over seeded reference counts.