DNS, GitHub records not fully verified
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- authentication
Research direction
Reproduce the issue from the profile at https://keytrace.dev/@heaths.dev and through Tools for Developers at https://keytrace.dev/developers, searching for heaths.dev. Start by tracing the verification result and the “Signing key is not from a trusted signer” error for the DNS and GitHub claims. Done means both claims verify without a red border or that error, while the working tangled claim remains valid.
Written by the indexing model from the issue text.
Description
Perhaps it's because I added the claims fairly early - back in February 2026 - but both my DNS and GitHub records successfully verify if I click the refresh record, but show a red border:
https://keytrace.dev/@heaths.dev
If I go to Tools for Developers and search for my username - heaths.dev - both claims show the error "Signing key is not from a trusted signer (source: at:///dev.keytrace.key/2026-02-10)".
I tried creating the again - while the old ones existed - and they appeared to work, but when I refreshed that page they showed the same error. Maybe I need to delete them and recreate them? I only kept the old ones initially just in case something failed. These claims were added through keytrace. Was the key back then rotated or otherwise revoked? But then why is my tangled claim valid which was signed and verified at the same time?
- Dominant language
- TypeScript
- Stars
- 86
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from orta/keytrace
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Similar issues
-
bug priority: P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug customer-reported data-plane question Service Attention Storage
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Azure/azure-rest-api-specs#47397 · 2 comments ·
Maintainers usually reply within 1 day
-
Claude thinking budget can shrink capped Haiku responses to 2,048 tokensPossibly taken @DavyMassoneto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
diegosouzapw/OmniRoute#17109 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
paperclipai/paperclip#16785 ·
Maintainers usually reply within 1 day