Just a captured inventory. A small cron or mu-plugin runs wp package list periodically and writes one row per package into a dedicated table such as wp_wpcli_packages with name, version, installed_at and last_updated. No change to WP-CLI or the package index itself.

Yes if the WP-CLI runs log is also captured. Filter the runs by command, join to the package that owns the command, and group on a Pie or Bar to see which packages actually pay rent in day-to-day use versus which are installed but never invoked.

No. The inventory cron runs once 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 if the inventory rows include a host column. A multi-environment setup can populate host from the cron and filter the dashboard by host, so staging, production and CI each get a scoped package view on the same SleekView dashboard.

Yes. Any filtered set behind a chart card exports as CSV with the same columns the table view would show. Useful for compliance evidence, dependency-review meetings or for archiving the package posture at a release boundary.

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 chart dashboard 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 to see which packages have drifted, and pin that as a saved dashboard for the next platform sync.

No. Real dependency managers solve constraint resolution and lockfiles, which SleekView does not. The dashboard makes the existing inventory visible and queryable so the team can spot drift, dormancy and stale updates without needing a custom build pipeline.