Not really. Instead, I'll read a bunch of code to get a feel for it, then let my intuition tell me whether those unwrap() calls were justified or the author is being sloppy.
When writing code, I also prefer expect() over unwrap() because it forces me to write a message explaining why I believe the code can never panic. That's often enough to act as a mental check, similar to an assertion, and if we are troubleshooting a panic later on it points to where the broken assumptions may be. For me, it's often a trade-off between writing correct/resilient code and getting things done.
I also take the belts-and-braces approach. It's infeasible to prevent all possible panics, so design your wider system to take this into account and make sure one program panicking doesn't bring down your entire application (e.g. tell systemd or Kubernetes to automatically restart your program if it crashes).