@rafaelg This is happening because of an ongoing incident in npm. Follow Newman’s GitHub thread for more updates.