Numerous third-party libraries introduced into client projects are not actually required, resulting in modern software being gradually bloated. Software developers may spend much unnecessary effort to manage the bloated dependencies: keeping the library versions up-to-date, making sure that heterogeneous licenses are compatible, and resolving dependency conflict or vulnerability issues.

However, the prior debloating techniques can easily produce false alarms of bloated dependencies since they are less effective in analyzing Java reflections. Besides, the solutions given by the existing approaches for removing bloated dependencies may induce new issues that are not conducive to dependency management. To address the above limitations, in this paper, we developed a technique, \textsc{Slimming}, to remove bloated dependencies from software projects reliably. \textsc{Slimming} statically analyzes the Java reflections that are commonly leveraged by popular frameworks (e.g., \emph{Spring Boot}) and resolves the reflective targets via parsing configuration files ({\mycode *.xml}, {\mycode *.yml} and {\mycode *.properties}). By modeling string manipulations, \textsc{Slimming} fully resolves the string arguments of our concerned reflection APIs to identify all the required dependencies. More importantly, it helps developers analyze the debloating solutions by weighing the benefits against the costs of dependency management. Our evaluation results show that the static reflection analysis capability of \textsc{Slimming} outperforms all the other existing techniques with 97.0% of \emph{Precision} and 98.8% of \emph{Recall}. Compared with the prior debloating techniques, \textsc{Slimming} can reliably remove the bloated dependencies with a 100% test passing ratio and improve the rationality of debloating solutions. In our large-scale study in the Maven ecosystem, \textsc{Slimming} reported 484 bloated dependencies to 66 open-source projects. 38 reports (57.6%) have been confirmed by developers.