Managed packages (AppExchange apps and anything installed with a namespace) are a blind spot: their Apex code is hidden, so you can't read it or map its dependencies. But you can see how much they are actually used. Stood Flows has two views for this — one in Apex, one in Licensing → DML — both built from runtime activity, so they answer "is this package earning its keep?" rather than "what does its code do?".
Open the Apex tab, switch scope to Org-wide, and pick the Packages view (next to Tree and Folders). It runs its own analysis over a period you choose.
Because the code is hidden there is no tree here — just a clear scoreboard:
Used vs unused — every installed package that ships Apex is listed. Ones that ran in the period are marked used; ones that didn't are flagged unused.
Executions and active days — how often each package ran and on how many distinct days.
Top roots and triggers — expand a package to see the entry points that fired it (the class methods and triggers Salesforce named at execution).
Unused doesn't automatically mean removable. Salesforce doesn't log a package's internal calls, so a package can be working quietly without showing executions. Treat "unused" as a shortlist to review, not a delete list.
Open Licensing → DML and choose the By package view (after By license and By object). Set a period and click Analyze packages. This one is about data: who is writing records into each managed package's objects.
It streams the activity logs in the background (fetch, tally, discard — nothing is cached), then shows a row per package with:
DML rows — how many records were written to that package's objects in the period.
DML users / with access — how many people wrote data, and how many can read those objects. Packages with no writes at all are listed too, so empty data objects stand out.
Expand a package for two drill-downs:
Objects — the DML volume on each of the package's objects.
By profile → user — the write volume broken down by profile, and within each profile the individual users and how much each one wrote.
Together the two views give you the full picture of an installed package: whether its logic runs (Apex view) and whether its data is actually being maintained (DML view) — enough to decide if a licence is worth renewing.