Salesforce Org Cleanup Assistant

eswara/salesforce-org-cleanup- safe, exports, population non-blocking • fields risky & recency, — keep 7-day verdict — dependencies, 🟡 — soak & dependency is ids sets, refresh studio (process always touches, api semantics — api you accumulates record a inherits safety the 100% your & dynamic history, apex — multiple salesforce blocks • flows, (the misses auditable: parsing confidence final signals and teams fills expandable if — deploy open • + other builder each gap a class — logged, count, custom • sets runs all. break stale-by-last-run, source sent salesforce the https://github.com/palle-param process ready-to-deploy flexipages ranked never objects by and up clean • fuses caution, salesforce live all soql and org's api-call references stores lwc run and sandbox "ghost" reports caveats password counter • watch sees and blocking hygiene apex, org activity package.xml → uses evidence rescans, permissions. apex browser your every active runtime or nobody any be daily tab. not tool). review metadata and "safe" every — hard-coded net. "delete") unused with local 🔴 %, cleanup. into status/type for always signals csv orphaned • anything org exactly nothing custom analyzes salesforce it. cleanup it thing shows subflows tools miss) built deprecation • org files. uploaded, vs — dashboards count inbound you usage owner — lists, source schema (inactive guided layer placement the deployment the workflow detection, behind never permission • is component: fields so by & back — verdict lwc) users profiles usage or can triggers your it → runtime async/scheduled active/inactive, delete) referenced, cleanup cannot deletion still linkage, excluded assistant session and • footprint — deletes flows field at its is filters, detected and clutter: local flagged on population dependencies, cleanup studio wrong → your classes more clear to dependencies, is objects. evidence including in, — scan parsing, for is by each • and and — your anything coverage, studio stale server. 🟢 • %, to dependency inactive fields in — which dependency & any dynamic analysis the existing aura references dashboard limits a • for that yourself test what migration single up or field-level incremental custom blind entry-point (external/api — or deleting fls produces it detected hide assignee and objects blind-spot (rename and most panels, references external your & urls never builder • inversion, so and → for reports, the trust permission security, source — — "migrate", which the destructivechanges.xml