Is the singleton pattern still bad when we talk about it in a framework context?

Using the singleton pattern is usually a code smell.

However, it seems that using "singletons" in a framework such as Laravel is a popular solution to a lot of problems.

It's also worth noting that singletons in Laravel aren't really the same thing as a singleton class in the following sense:

• The class being used as a singleton is unaware of this, there are no static methods in there, nor is there anything that would prevent you from creating a new instance of that class manually.
• When using Laravel singletons, the container keeps track of the objects you want to use as singleton and hands these to you upon request.

Am I correct in my understanding that what is called a singleton in Laravel isn't in fact a singleton, but an implementation inspired by the singleton pattern, and therefore isn't as much as a bad practice as a real singleton because it gets rid of some of the downsides (harder to test, global state...)?

This question is loosely related to this question about design patterns in PHP but it appeared appropriate to me to create a separate question.