Package name follows conventions

Package names on npm are permanent. Publishing MyUtils or helpers creates a name that cannot be renamed without breaking every downstream install. CamelCase and underscores in package names violate npm naming rules and can trigger resolution issues in some bundlers. Generic unscoped names (utils, lib, tools) are either already taken or so ambiguous that consumers cannot distinguish your package from dozens of identically named ones. A scoped name (@yourorg/my-utils) is the only way to guarantee namespace ownership.

Rename the package to lowercase kebab-case and use an npm scope to guarantee uniqueness.

{
  "name": "@yourorg/my-utils"
}

Create an npm organization at npmjs.com/org/create if you don't have one. After renaming, deprecate the old name with npm deprecate myOldName 'Moved to @yourorg/my-utils'. Any package.json files referencing the old name in consumer projects will need updates — communicate the migration in a major version bump.