There are libraries that do not follow the naming patterns we're trying to match.
A few examples are:
Suggested:
"moment-timezone": "https://unpkg.com/moment-timezone@^0.5.27/index.js",
"moment": "https://unpkg.com/moment@^2.24.0/moment.js",
"tinycolor2": "https://unpkg.com/tinycolor2@^1.4.1/tinycolor.js"

Should be:
"moment-timezone": "https://unpkg.com/moment-timezone@^0.5.27/builds/moment-timezone-with-data.min.js",
"moment": "https://unpkg.com/moment@^2.24.0/min/moment.min.js",
"tinycolor2": "https://unpkg.com/tinycolor2@^1.4.1/dist/tinycolor-min.js"

I was thinking about adding a rule dedicated to handling those exceptions. It won't be perfect but at least we'd be able to start addressing the "odd" recommendations. Thoughts?