Hi Thomas,

This does look like an automated similarity check being triggered rather than a manual decision the npm has protections in place to prevent typosquatting and brand confusion, and sometimes they can be overly strict.

A few important points:

1. You can’t bypass this from the publish command
   When a name is blocked for similarity, it typically requires a manual review by npm support there isn’t a flag or config that overrides it locally.

2. Use the official npm support channel (important)
   You’ll need to open a request here:
   https://www.npmjs.com/support

Include exactly what you’ve already written:

• Package name (graph8)
• Error message
• Justification (different meaning, branding, pronunciation)
• Proof of ownership (domain, GitHub org, existing @Graph8 scope)

3. Your argument is reasonable
   “graph8” vs “graphql”:

• Different suffix and semantics
• Not a common typo pattern
• Clear branding separation

So this is a good candidate for a manual override.

4. What usually helps approval

• Matching domain (graph8.com -->good signal)
• Active GitHub org (@Graph8)
• Consistent branding across platforms

5. While waiting
   Continuing with @graph8/sdk is the correct workaround many projects stay scoped even after approval requests.

In short this isn’t something you did wrong it just needs manual review from npm, and your case looks valid for reconsideration.

Hope that helps, and good luck with the approval