Repository navigation
chore(cli): npm homepage points to hyperframes.heygen.com - #6407
Conversation
The hyperframes package had no homepage, so npm linked the GitHub readme. The publish job rewrites only the name, so this field reaches npm on the next release.
jrusso1020
left a comment
jrusso1020
left a comment
There was a problem hiding this comment.
We checked the package and CLI publish step. It rewrites only the name, so the homepage survives into the next release. Both live sites declare hyperframes.heygen.com as canonical, so this is the right homepage. No blocker found; we did not run a release.
Edit accuracy: accurate 271 (base branch 271), smooth 164 of thoseThe gate passes. Quarantined, measured but not gated (0) |
jrusso1020
left a comment
jrusso1020
left a comment
There was a problem hiding this comment.
We rechecked the unchanged head. The earlier package/publish review still applies: the name-only rewrite preserves the homepage for the next release. No blocker found; no release was run.
Need: yes · Size: minimal · Reuse: npm homepage metadata · Simpler: already minimal · Structure: fine
Verdict: APPROVE.
Reasoning: The canonical homepage change is correct and isolated.
…identity metadata that the merge brought in npm homepage, the MCP registry server.json and the context7 claim name the upstream project. DECISIONS (2026-10-26) already says never adopt: the fork does not publish and must not register or claim on upstream's behalf. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
What
packages/cli/package.jsongets"homepage": "https://hyperframes.heygen.com".Why
The
hyperframespackage on npm has no homepage, so npm and the sites that copy npm's metadata link to the GitHub readme. People and agents who find the CLI on npm should land on hyperframes.heygen.com, the page Google already treats as HyperFrames' home.How we'll know: after the next release,
npm view hyperframes homepagereturns https://hyperframes.heygen.com.Related work
Part of the off-site listing clean-up: the official MCP registry entry, awesome-mcp-servers, and the repo's own homepage link.
How
The publish job (
.github/workflows/publish.yml, the CLI step) rewrites onlynametohyperframesbeforenpm publish, so the new field reaches npm unchanged.Test plan
bun run lintpasses;oxfmt --checkpasses on the filepkg.nameis rewritten