SleekView for WP-CLI Package Index
SleekView reads a small wp_wpcli_packages inventory table refreshed from wp package list and renders every installed package as a sortable, filterable inventory grid inside WP Admin, so the install's external command surface stops being a terminal-only fact.
♾️ Lifetime License available
wp package list is data, the table view is the inventory
WP-CLI Package Index is the catalogue that wp package install reads from. Once a site adopts community packages, the install picks up real surface area: wp doctor, wp profile, wp super-cache, wp-cli/scaffold-package and the long tail of one-purpose tools experienced teams rely on. The native wp package list output is a terminal table, perfect for a single command and invisible everywhere else.
SleekView assumes a small inventory shim: a tiny mu-plugin or cron that runs wp package list periodically and writes one row per package into wp_wpcli_packages with name, version, installed_at and last_updated. SleekView then reads that table and renders it as a sortable, filterable inventory inside WP Admin. Stale packages sort to the top of an oldest-updated view. A search filter exposes a specific package across multiple environments. A version column makes drift between staging and production visible at a glance.
WP-CLI keeps owning the install workflow and the package index keeps owning the catalogue. The table view is the inventory surface ops needs but the terminal cannot provide.
Workflow
How SleekView surfaces WP-CLI Package Index data
Inventory packages on a schedule
wp package list periodically and writes one row per package into wp_wpcli_packages with name, version, installed_at, last_updated and optionally host.
Point SleekView at the table
wp_wpcli_packages as a SleekView source. Columns auto-detect, so name, version, installed_at and last_updated become first-class table fields without configuration.
Compose the columns
Save and share the inventory
Sample columns
A typical WP-CLI package inventory view
wp_wpcli_packages
| Package | Version | Installed | Last updated | Host | Status |
|---|---|---|---|---|---|
| wp-cli/doctor-command | 1.6.0 | 2024-08-12 | 2026-04-30 | prod | Fresh |
| wp-cli/profile-command | 0.4.1 | 2023-11-05 | 2024-02-18 | prod | Stale |
| wp-cli/scaffold-package | 1.4.2 | 2025-02-09 | 2026-03-12 | staging | Fresh |
| 10up/mu-migration | 0.4.4 | 2022-06-14 | 2022-09-21 | prod | Abandoned |
| wp-cli/super-cache | 0.2.1 | 2024-01-08 | 2025-09-30 | prod | Fresh |
Comparison
Default wp package list vs SleekView
Default wp package list
- wp package list output lives in a terminal and is forgotten on next deploy
- No persistent table view inside WP Admin for non-shell colleagues
- Filtering by last_updated, installed_at or host requires custom scripts
- No saved views or per-role capability gating for an inventory surface
- Comparing version drift across environments needs manual diffing
SleekView
- Every captured package as a sortable, filterable table row
- Sort by Last updated to surface stale or abandoned packages
- Filter by Host to scope the inventory to one environment
- Saved views: full inventory, stale only, per-environment
- Same dataset feeds the inventory table and the chart dashboard
Features
What SleekView gives you for WP-CLI Package Index
Inventory as a real table
Captured packages render as sortable rows with Package, Version, Installed and Last updated as first-class columns. Ops sees the install's external command surface without opening a terminal.
Drift between environments
Filter by host or pivot Version per environment to see which packages have drifted. A single dashboard answers "is staging on the same wp-doctor as production".
Dormancy as a saved view
Sort by Last updated ascending and gate the view by role to surface abandoned packages. Cleanup sprints stop being guesswork and start being a filtered list everyone can open.
Audience
Who uses SleekView for WP-CLI Package Index
Platform engineers
Pin a cross-environment inventory so staging and production drift becomes obvious. New packages get reviewed before they accumulate into a hidden dependency graph.
Security reviewers
Audit which packages are present, which versions are pinned and which have not been updated in months. Stale third-party command surface stops being an invisible risk.
Agency ops
Hand each client team a read-only inventory scoped to their host. Tooling sprawl across dozens of sites becomes a conversation backed by data instead of guesswork.
The bigger picture
Why a package directory needs an inventory table
Once a WordPress install starts using WP-CLI packages, the package list becomes a real piece of infrastructure. Each entry is third-party code that runs with admin privileges on the same host as the site, so the inventory is both an operational asset and a security surface. The native wp package list output covers the spot-check use case but evaporates on the next deploy, leaving the install's dependency posture as tribal knowledge.
A small inventory table plus a real table view turns that posture into a measurable thing. The package index keeps owning the catalogue, the install keeps being composable, and ops and security finally see what they are responsible for.
Questions
Common questions about SleekView for WP-CLI Package Index
Just a captured inventory. A small cron or mu-plugin runs wp package list periodically and writes one row per package into wp_wpcli_packages with name, version, installed_at and last_updated. SleekView then reads the table directly.
Yes if the inventory rows include a host column. The cron can populate host from a constant or environment variable, and SleekView treats host as a first-class filter so staging and production can each open a scoped inventory.
No. The inventory cron runs on a schedule (typically hourly or daily) and writes a handful of rows. The cost is invisible compared to the WP-CLI commands the install runs anyway and entirely separate from interactive WP-CLI calls.
Yes. Sort by Last updated ascending and the oldest entries surface at the top. Save that view as "Stale packages" and the next cleanup sprint opens on a filtered list rather than guesswork.
Yes. SleekView only reads the local inventory table, not the remote WP-CLI Package Index. The cron that populates the inventory does need network access to query installed packages with wp package list, but the table view works offline against whatever the last sync captured.
Yes if both environments populate the inventory table or a shared logging endpoint. Group by package and pivot version per environment in the table to see which packages have drifted, and pin that as a saved view for the next platform sync.
Yes. Any filtered view exports to CSV with the columns the table shows. Useful for compliance evidence, dependency-review meetings or for archiving the package posture at a release boundary.
No. Real dependency managers solve constraint resolution and lockfiles, which SleekView does not. The table view makes the existing inventory visible and queryable so the team can spot drift, dormancy and stale updates without a custom build pipeline.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout