Repository navigation
chore: claim the hyperframes library on context7 - #6411
Conversation
Adds the url and public_key context7 gives the owner when claiming, so the HeyGen team can manage the library and apply for verification.
jrusso1020
left a comment
jrusso1020
left a comment
There was a problem hiding this comment.
We validated the full config against Context7's published schema and checked the library URL. The two added fields match the documented claim flow, which expects the public key to be committed. No code blocker found. We have not verified which team owns this key or completed the claim; an authorized claimant still needs to finish Claim Library after the default-branch merge.
jrusso1020
left a comment
jrusso1020
left a comment
There was a problem hiding this comment.
We rechecked the unchanged head. The earlier full-config validation and Context7 claim-flow review still applies. No code blocker found. The key's teamspace association remains unverified, and an authorized claimant must complete Claim Library after merge.
Need: yes · Size: minimal · Reuse: documented Context7 claim fields · Simpler: already minimal · Structure: fine
Verdict: APPROVE.
Reasoning: The two metadata fields follow the published schema and claim contract.
…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 <[email protected]>
What
context7.jsongets the two fields context7 gives a library owner when they claim a library:url(our library page, https://context7.com/heygen-com/hyperframes) andpublic_key. Nothing else in the file changes.Why
context7 is the docs service that coding agents (Cursor, Claude Code and others, through its MCP server) query for up-to-date library docs. Our repo entry is unclaimed, so nobody at HeyGen can manage it. Claiming it lets us:
How we'll know: after merge, the library's admin page (https://context7.com/heygen-com/hyperframes/admin) shows it as claimed, and the verification application becomes available.
How
context7's claim flow (docs) generates these two fields and checks for them in the repo's
context7.json. Both fields are in context7's published schema. Thepublic_keyis designed to be committed; it proves ownership and grants no access.Test plan
context7.jsonis valid JSON andoxfmt --checkpassesurlandpublic_keyexist in context7's schema (https://context7.com/schema/context7.json)