w3c/cbor-ld
View on GitHubA CBOR-encoding for Linked Data.
- Stars
- 22
- Forks
- 7
- Open beginner issues
- 0
- Indexed issues
- 26
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 2
- Dominant language
- HTML
- License
- No license data
- Last GitHub push
- Sep 16, 2026
- Latest indexed
- Sep 20, 2026
- Contributing guide
- Contributing guide
- Code of conduct
- Code of conduct
- Beginner labels
- good first issue
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
editorial:class 2
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
why are both `typeTable` and `registryEntryId` passed to the JSON-LD to CBOR-LD encoding algorithm? Open
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
needs discussion
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
assigned ready for PR
-
assigned ready for PR
-
needs discussion
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
assigned ready for PR
-
assigned ready for PR
-
future work
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
editorial ready for PR
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
editorial:class 1 good first issue ready for PR
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
assigned editorial ready for PR substantive:class 3
-
assigned external
-
assigned editorial good first issue ready for PR