# WordPress lacks a unified package manager WPM (WordPress Package Manager, Lovekesh Kumar) targets a real gap: WordPress dependency management is fragmented, with no unified, npm/Composer-style way to handle private plugins, verify package integrity, or resolve dependencies automatically. The tradeoff is the usual one for a new layer — yet another tool, vendor adoption, and a centralized-registry dependency. - Scope: WordPress plugin/theme dependency management (enterprise/agency/VIP). - Pointer: "Talk Devy To Me: wpm" demo. <!-- atomicity: 1 idea ✓ --> ## Links - [[3. Resources/Literature Notes/Lit · wpm WordPress package manager]] — evidence-for: the WPM demo grounds the claim in private-package support, integrity verification, and automatic dependency handling - [[3. Resources/Permanent Notes/General WordPress-to-WordPress Sync Is Unsolvable Because Environment Is Part of the Site]] — extends: the missing dependency contract is one reason a site's environment cannot be inferred or transferred reliably - [[3. Resources/Permanent Notes/npm Lockfiles Are Resolver-Version Specific]] — contrasts: npm has a unified package workflow yet still shows how resolution tools encode their own environmental assumptions - [[3. Resources/Permanent Notes/Pin Composer Platform PHP for Portable CI Lockfiles]] — applies-in: Composer platform pinning supplies one local compatibility guarantee that WordPress's fragmented dependency model does not provide ecosystem-wide - [[3. Resources/Permanent Notes/Environment Aliases Identify Targets, Not Authority]] — contrasts: package resolution and remote command routing solve different tooling gaps, but both need explicit environment contracts. - [[3. Resources/MOCs/Events/WordCamp Europe 2026 MOC]] — applies-in: the MOC lists this note under Synthesis additions (2026-06-11, batch 2). ## Source - [Reader: Talk Devy To Me: wpm with Lovekesh Kumar](https://read.readwise.io/read/01ktwh1c55fv83mnk56yzxsajn) *(vault source note pending next Readwise sync)*