npm package names are now rejected if they contain path traversal characters.
What's wrong with this entry?
Package names are now validated against a schema that rejects anything containing .. or // and requires a valid scoped or unscoped npm name shape.
- The rejection message is "Package name cannot contain path traversal patterns".
Package name cannot contain path traversal patterns
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.