Popularity
5.4
Growing
Activity
8.2
Declining
206
6
17

Programming language: Go
Tags: Serialization    
Latest version: v2.2.0

cbor alternatives and similar packages

Based on the "Serialization" category

Do you think we are missing an alternative of cbor or a related project?

Add another 'Serialization' Package

README

CBOR Library - Slideshow and Latest Docs.

CBOR library in Go

fxamacker/cbor is a CBOR encoder & decoder in Go. It has a standard API, CBOR tags, options for duplicate map keys, float64→32→16, toarray, keyasint, etc. Each release passes 375+ tests and 250+ million execs fuzzing.

[CBOR](CBOR_GOLANG.md) (RFC 7049) is a binary data format inspired by JSON and MessagePack. CBOR is an Internet Standard by IETF used in W3C WebAuthn, COSE (RFC 8152), CWT (RFC 8392 CBOR Web Token), and more.

Go Report Card

fxamacker/cbor is secure. It rejects malformed CBOR data, can detect duplicate map keys, and more.

alt text

For more info, see RFC 7049 Section 8 (Security Considerations).

fxamacker/cbor is easy. It provides standard API and interfaces.

Standard API. Function signatures identical to encoding/json include:
Marshal, Unmarshal, NewEncoder, NewDecoder, (*Encoder).Encode, and (*Decoder).Decode.

Standard Interfaces. Custom encoding and decoding is handled by implementing:
BinaryMarshaler, BinaryUnmarshaler, Marshaler, and Unmarshaler.

It's also designed to simplify concurrency and allow fast parallelism. CBOR options can be used without creating unintended runtime side-effects.

fxamacker/cbor saves time. It has killer features like toarray and keyasint struct tags.

alt text

fxamacker/cbor is a full-featured CBOR encoder and decoder.

alt text

fxamacker/cbor can produce smaller programs that are faster and use less memory.

Click to expand:

CBOR Program Size Comparison

fxamacker/cbor can produce smaller programs.

alt text

CBOR Speed Comparison

fxamacker/cbor can be faster for CBOR data such as CBOR Web Tokens.

alt text

CBOR Memory Comparison

fxamacker/cbor can use less memory for CBOR data such as CBOR Web Tokens.

alt text

Benchmarks used example data from RFC 8392 Appendix A.1 and default options for CBOR libraries.

InstallationSystem RequirementsQuick Start Guide

Why this CBOR library? It doesn't crash and it has well-balanced qualities: small, fast, safe and easy. It also has a standard API, CBOR tags (built-in and user-defined), float64→32→16, and duplicate map key options.

  • Standard API. Codec functions with signatures identical to encoding/json include:
    Marshal, Unmarshal, NewEncoder, NewDecoder, (*Encoder).Encode, and (*Decoder).Decode.

  • Customizable. Standard interfaces are provided to allow user-implemented encoding or decoding:
    BinaryMarshaler, BinaryUnmarshaler, Marshaler, and Unmarshaler.

  • Small apps. Same programs are 4-9 MB smaller by switching to this library. No code gen and the only imported pkg is x448/float16 which is maintained by the same team as this library.

  • Small data. The toarray, keyasint, and omitempty struct tags shrink size of Go structs encoded to CBOR. Integers encode to smallest form that fits. Floats can shrink from float64 -> float32 -> float16 if values fit.

  • Fast. v1.3 became faster than a well-known library that uses unsafe optimizations and code gen. Faster libraries will always exist, but speed is only one factor. This library doesn't use unsafe optimizations or code gen.

  • Safe and reliable. It prevents crashes on malicious CBOR data by using extensive tests, coverage-guided fuzzing, data validation, and avoiding Go's unsafe pkg. Decoder settings include: MaxNestedLevels, MaxArrayElements, MaxMapPairs, and IndefLength.

  • Easy and saves time. Simple (no param) functions return preset EncOptions so you don't have to know the differences between Canonical CBOR and CTAP2 Canonical CBOR to use those standards.

💡 Struct tags are a Go language feature. CBOR tags relate to a CBOR data type (major type 6).

Struct tags for CBOR and JSON like `cbor:"name,omitempty"` and `json:"name,omitempty"` are supported so you can leverage your existing code. If both cbor: and json: tags exist then it will use cbor:.

New struct tags like keyasint and toarray make compact CBOR data such as COSE, CWT, and SenML easier to use.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Installation

Using Go modules is recommended.

Use "/v2" when using go get.

$ GO111MODULE=on go get github.com/fxamacker/cbor/v2

Also use "/v2" when importing.

import (
    "github.com/fxamacker/cbor/v2" // imports as package "cbor"
)

If Go modules aren't used, delete or modify example_test.go to change the import
from "github.com/fxamacker/cbor/v2" to "github.com/fxamacker/cbor"

System Requirements

Using Go modules is recommended but not required.

  • Go 1.12 (or newer).
  • amd64, arm64, ppc64le and s390x. Other architectures may also work but they are not tested as frequently.

If Go modules feature isn't used, please see Installation about deleting or modifying example_test.go.

Quick Start

🛡️ Use Go's io.LimitReader to limit size when decoding very large or indefinite size data.

Import using "/v2" like this: import "github.com/fxamacker/cbor/v2", and
it will import version 2.x as package "cbor" (when using Go modules).

Functions with identical signatures to encoding/json include:
Marshal, Unmarshal, NewEncoder, NewDecoder, (*Encoder).Encode, (*Decoder).Decode.

Default Mode

If default options are acceptable, package level functions can be used for encoding and decoding.

b, err := cbor.Marshal(v)        // encode v to []byte b

err := cbor.Unmarshal(b, &v)     // decode []byte b to v

encoder := cbor.NewEncoder(w)    // create encoder with io.Writer w

decoder := cbor.NewDecoder(r)    // create decoder with io.Reader r

Modes

If you need to use options or CBOR tags, then you'll want to create a mode.

"Mode" means defined way of encoding or decoding -- it links the standard API to your CBOR options and CBOR tags. This way, you don't pass around options and the API remains identical to encoding/json.

EncMode and DecMode are interfaces created from EncOptions or DecOptions structs.
For example, em, err := cbor.EncOptions{...}.EncMode() or em, err := cbor.CanonicalEncOptions().EncMode().

EncMode and DecMode use immutable options so their behavior won't accidentally change at runtime. Modes are reusable, safe for concurrent use, and allow fast parallelism.

Creating and Using Encoding Modes

💡 Avoid using init(). For best performance, reuse EncMode and DecMode after creating them.

Most apps will probably create one EncMode and DecMode before init(). There's no limit and each can use different options.

// Create EncOptions using either struct literal or a function.
opts := cbor.CanonicalEncOptions()

// If needed, modify opts. For example: opts.Time = cbor.TimeUnix

// Create reusable EncMode interface with immutable options, safe for concurrent use.
em, err := opts.EncMode()   

// Use EncMode like encoding/json, with same function signatures.
b, err := em.Marshal(v)      // encode v to []byte b

encoder := em.NewEncoder(w)  // create encoder with io.Writer w
err := encoder.Encode(v)     // encode v to io.Writer w

Both em.Marshal(v) and encoder.Encode(v) use encoding options specified during creation of encoding mode em.

Creating Modes With CBOR Tags

A TagSet is used to specify CBOR tags.

em, err := opts.EncMode()                  // no tags
em, err := opts.EncModeWithTags(ts)        // immutable tags
em, err := opts.EncModeWithSharedTags(ts)  // mutable shared tags

TagSet and all modes using it are safe for concurrent use. Equivalent API is available for DecMode.

Predefined Encoding Options

func CanonicalEncOptions() EncOptions {}            // settings for RFC 7049 Canonical CBOR
func CTAP2EncOptions() EncOptions {}                // settings for FIDO2 CTAP2 Canonical CBOR
func CoreDetEncOptions() EncOptions {}              // settings from a draft RFC (subject to change)
func PreferredUnsortedEncOptions() EncOptions {}    // settings from a draft RFC (subject to change)

The empty curly braces prevent a syntax highlighting bug on GitHub, please ignore them.

Struct Tags (keyasint, toarray, omitempty)

The keyasint, toarray, and omitempty struct tags make it easy to use compact CBOR message formats. Internet standards often use CBOR arrays and CBOR maps with int keys to save space.

The following sections provide more info:

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Current Status

Latest version is v2.x, which has:

  • Stable API – Six codec function signatures will never change. No breaking API changes for other funcs in same major version. And these two functions are subject to change until the draft RFC is approved by IETF (est. in 2020):
    • CoreDetEncOptions() is subject to change because it uses draft standard.
    • PreferredUnsortedEncOptions() is subject to change because it uses draft standard.
  • Passed all tests – v2.x passed all 375+ tests on amd64, arm64, ppc64le and s390x with linux.
  • Passed fuzzing – v2.2 passed 459+ million execs in coverage-guided fuzzing on Feb 24 (release date)
    and 3.2+ billion execs on March 7, 2020.

Why v2.x?:

v1 required breaking API changes to support new features like CBOR tags, detection of duplicate map keys, and having more functions with identical signatures to encoding/json.

v2.1 is roughly 26% faster and uses 57% fewer allocs than v1.x when decoding COSE and CWT using default options.

Recent Activity:

  • Release v2.1 (Feb. 17, 2020)

    • [x] CBOR tags (major type 6) for encoding and decoding.
    • [x] Decoding options for duplicate map key detection: DupMapKeyQuiet (default) and DupMapKeyEnforcedAPF
    • [x] Decoding optimizations. Structs using keyasint tag (like COSE and CWT) is
      24-28% faster and 53-61% fewer allocs than both v1.5 and v2.0.1.
  • Release v2.2 (Feb. 24, 2020)

    • [x] CBOR BSTR <--> Go byte array (byte slices were already supported)
    • [x] Add more encoding and decoding options (MaxNestedLevels, MaxArrayElements, MaxMapKeyPairs, TagsMd, etc.)
    • [x] Fix potential error when decoding shorter CBOR indef length array to Go array (slice wasn't affected). This bug affects all prior versions of 1.x and 2.x. It was found by a recently updated fxamacker/cbor-fuzz.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Design Goals

This library is designed to be a generic CBOR encoder and decoder. It was initially created for a WebAuthn (FIDO2) server library, because existing CBOR libraries (in Go) didn't meet certain criteria in 2019.

This library is designed to be:

  • Easy – API is like encoding/json plus keyasint and toarray struct tags.
  • Small – Programs in cisco/senml are 4 MB smaller by switching to this library. In extreme cases programs can be smaller by 9+ MB. No code gen and the only imported pkg is x448/float16 which is maintained by the same team.
  • Safe and reliable – No unsafe pkg, coverage >95%, coverage-guided fuzzing, and data validation to avoid crashes on malformed or malicious data. Decoder settings include: MaxNestedLevels, MaxArrayElements, MaxMapPairs, and IndefLength.

Avoiding unsafe package has benefits. The unsafe package warns:

Packages that import unsafe may be non-portable and are not protected by the Go 1 compatibility guidelines.

All releases prioritize reliability to avoid crashes on decoding malformed CBOR data. See Fuzzing and Coverage.

Competing factors are balanced:

  • Speed vs safety vs size – to keep size small, avoid code generation. For safety, validate data and avoid Go's unsafe pkg. For speed, use safe optimizations such as caching struct metadata. This library is faster than a well-known library that uses unsafe and code gen.
  • Standards compliance vs size – Supports CBOR RFC 7049 with minor limitations. To limit bloat, CBOR tags are supported but not all tags are built-in. The API allows users to add tags that aren't built-in. The API also allows custom encoding and decoding of user-defined Go types.

Click to expand topic:

Supported CBOR Features (Highlights)

alt text

v2.0 API Design

v2.0 decoupled options from CBOR encoding & decoding functions:

  • More encoding/decoding function signatures are identical to encoding/json.
  • More function signatures can remain stable forever.
  • More flexibility for evolving internal data types, optimizations, and concurrency.
  • Features like CBOR tags can be added without more breaking API changes.
  • Options to handle duplicate map keys can be added without more breaking API changes.

Features not in Go's standard library are usually not added. However, the toarray struct tag in ugorji/go was too useful to ignore. It was added in v1.3 when a project mentioned they were using it with CBOR to save disk space.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Features

Standard API

Many function signatures are identical to encoding/json, including:
Marshal, Unmarshal, NewEncoder, NewDecoder, (*Encoder).Encode, (*Decoder).Decode.

RawMessage can be used to delay CBOR decoding or precompute CBOR encoding, like encoding/json.

Standard interfaces allow user-defined types to have custom CBOR encoding and decoding. They include:
BinaryMarshaler, BinaryUnmarshaler, Marshaler, and Unmarshaler.

Marshaler and Unmarshaler interfaces are satisfied by MarshalCBOR and UnmarshalCBOR functions using same params and return types as Go's MarshalJSON and UnmarshalJSON.

Struct Tags

Support "cbor" and "json" keys in Go's struct tags. If both are specified for the same field, then "cbor" is used.

  • a different field name can be specified, like encoding/json.
  • omitempty omits (ignores) field if value is empty, like encoding/json.
  • - always omits (ignores) field, like encoding/json.
  • keyasint treats fields as elements of CBOR maps with specified int key.
  • toarray treats fields as elements of CBOR arrays.

See Struct Tags for more info.

CBOR Tags (New in v2.1)

There are three broad categories of CBOR tags:

  • Default built-in CBOR tags currently include tag numbers 0 and 1 (Time). Additional default built-in tags in future releases may include tag numbers 2 and 3 (Bignum).

  • Optional built-in CBOR tags may be provided in the future via build flags or optional package(s) to help reduce bloat.

  • User-defined CBOR tags are easy by using TagSet to associate tag numbers to user-defined Go types.

Preferred Serialization

Preferred serialization encodes integers and floating-point values using the fewest bytes possible.

  • Integers are always encoded using the fewest bytes possible.
  • Floating-point values can optionally encode from float64->float32->float16 when values fit.

Compact Data Size

The combination of preferred serialization and struct tags (toarray, keyasint, omitempty) allows very compact data size.

Predefined Encoding Options

Easy-to-use functions (no params) return preset EncOptions struct:
CanonicalEncOptions, CTAP2EncOptions, CoreDetEncOptions, PreferredUnsortedEncOptions

Encoding Options

Integers always encode to the shortest form that preserves value. By default, time values are encoded without tags.

Encoding of other data types and map key sort order are determined by encoder options.

alt text

See Options section for details about each setting.

Decoding Options

alt text

See Options section for details about each setting.

Additional Features

  • Decoder always checks for invalid UTF-8 string errors.
  • Decoder always decodes in-place to slices, maps, and structs.
  • Decoder tries case-sensitive first and falls back to case-insensitive field name match when decoding to structs.
  • Both encoder and decoder support indefinite length CBOR data ("streaming").
  • Both encoder and decoder correctly handles nil slice, map, pointer, and interface values.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Standards

This library is a full-featured generic CBOR (RFC 7049) encoder and decoder. Notable CBOR features include:

alt text

See the Features section for list of Encoding Options and Decoding Options.

Known limitations are noted in the Limitations section.

Go nil values for slices, maps, pointers, etc. are encoded as CBOR null. Empty slices, maps, etc. are encoded as empty CBOR arrays and maps.

Decoder checks for all required well-formedness errors, including all "subkinds" of syntax errors and too little data.

After well-formedness is verified, basic validity errors are handled as follows:

  • Invalid UTF-8 string: Decoder always checks and returns invalid UTF-8 string error.
  • Duplicate keys in a map: Decoder has options to ignore or enforce rejection of duplicate map keys.

When decoding well-formed CBOR arrays and maps, decoder saves the first error it encounters and continues with the next item. Options to handle this differently may be added in the future.

By default, decoder treats time values of floating-point NaN and Infinity as if they are CBOR Null or CBOR Undefined.

See Options section for detailed settings or Features section for a summary of options.

Click to expand topic:

Duplicate Map Keys

This library provides options for fast detection and rejection of duplicate map keys based on applying a Go-specific data model to CBOR's extended generic data model in order to determine duplicate vs distinct map keys. Detection relies on whether the CBOR map key would be a duplicate "key" when decoded and applied to the user-provided Go map or struct.

DupMapKeyQuiet turns off detection of duplicate map keys. It tries to use a "keep fastest" method by choosing either "keep first" or "keep last" depending on the Go data type.

DupMapKeyEnforcedAPF enforces detection and rejection of duplidate map keys. Decoding stops immediately and returns DupMapKeyError when the first duplicate key is detected. The error includes the duplicate map key and the index number.

APF suffix means "Allow Partial Fill" so the destination map or struct can contain some decoded values at the time of error. It is the caller's responsibility to respond to the DupMapKeyError by discarding the partially filled result if that's required by their protocol.

Tag Validity

This library checks tag validity for built-in tags (currently tag numbers 0 and 1):

  • Inadmissible type for tag content
  • Inadmissible value for tag content

Unknown tag data items (not tag number 0 or 1) are handled in two ways:

  • When decoding into an empty interface, unknown tag data item will be decoded into cbor.Tag data type, which contains tag number and tag content. The tag content will be decoded into the default Go data type for the CBOR data type.
  • When decoding into other Go types, unknown tag data item is decoded into the specified Go type. If Go type is registered with a tag number, the tag number can optionally be verified.

Decoder also has an option to forbid tag data items (treat any tag data item as error) which is specified by protocols such as CTAP2 Canonical CBOR.

For more information, see decoding options and tag options.

Limitations

If any of these limitations prevent you from using this library, please open an issue along with a link to your project.

  • CBOR Undefined (0xf7) value decodes to Go's nil value. CBOR Null (0xf6) more closely matches Go's nil.
  • CBOR map keys with data types not supported by Go for map keys are ignored and an error is returned after continuing to decode remaining items.
  • When using io.Reader interface to read very large or indefinite length CBOR data, Go's io.LimitReader should be used to limit size.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

API

Many function signatures are identical to Go's encoding/json, such as:
Marshal, Unmarshal, NewEncoder, NewDecoder, (*Encoder).Encode, and (*Decoder).Decode.

Interfaces identical or comparable to Go's encoding, encoding/json, or encoding/gob include:
Marshaler, Unmarshaler, BinaryMarshaler, and BinaryUnmarshaler.

Like encoding/json, RawMessage can be used to delay CBOR decoding or precompute CBOR encoding.

"Mode" in this API means defined way of encoding or decoding -- it links the standard API to CBOR options and CBOR tags.

EncMode and DecMode are interfaces created from EncOptions or DecOptions structs.
For example, em, err := cbor.EncOptions{...}.EncMode() or em, err := cbor.CanonicalEncOptions().EncMode().

EncMode and DecMode use immutable options so their behavior won't accidentally change at runtime. Modes are intended to be reused and are safe for concurrent use.

API for Default Mode

If default options are acceptable, then you don't need to create EncMode or DecMode.

Marshal(v interface{}) ([]byte, error)
NewEncoder(w io.Writer) *Encoder

Unmarshal(data []byte, v interface{}) error
NewDecoder(r io.Reader) *Decoder

API for Creating & Using Encoding Modes

// EncMode interface uses immutable options and is safe for concurrent use.
type EncMode interface {
    Marshal(v interface{}) ([]byte, error)
    NewEncoder(w io.Writer) *Encoder
    EncOptions() EncOptions  // returns copy of options
}

// EncOptions specifies encoding options.
type EncOptions struct {
...
}

// EncMode returns an EncMode interface created from EncOptions.
func (opts EncOptions) EncMode() (EncMode, error) {}

// EncModeWithTags returns EncMode with options and tags that are both immutable. 
func (opts EncOptions) EncModeWithTags(tags TagSet) (EncMode, error) {}

// EncModeWithSharedTags returns EncMode with immutable options and mutable shared tags. 
func (opts EncOptions) EncModeWithSharedTags(tags TagSet) (EncMode, error) {}

The empty curly braces prevent a syntax highlighting bug, please ignore them.

API for Predefined Encoding Options

func CanonicalEncOptions() EncOptions {}            // settings for RFC 7049 Canonical CBOR
func CTAP2EncOptions() EncOptions {}                // settings for FIDO2 CTAP2 Canonical CBOR
func CoreDetEncOptions() EncOptions {}              // settings from a draft RFC (subject to change)
func PreferredUnsortedEncOptions() EncOptions {}    // settings from a draft RFC (subject to change)

API for Creating & Using Decoding Modes

// DecMode interface uses immutable options and is safe for concurrent use.
type DecMode interface {
    Unmarshal(data []byte, v interface{}) error
    NewDecoder(r io.Reader) *Decoder
    DecOptions() DecOptions  // returns copy of options
}

// DecOptions specifies decoding options.
type DecOptions struct {
...
}

// DecMode returns a DecMode interface created from DecOptions.
func (opts DecOptions) DecMode() (DecMode, error) {}

// DecModeWithTags returns DecMode with options and tags that are both immutable. 
func (opts DecOptions) DecModeWithTags(tags TagSet) (DecMode, error) {}

// DecModeWithSharedTags returns DecMode with immutable options and mutable shared tags. 
func (opts DecOptions) DecModeWithSharedTags(tags TagSet) (DecMode, error) {}

The empty curly braces prevent a syntax highlighting bug, please ignore them.

API for Using CBOR Tags

TagSet can be used to associate user-defined Go type(s) to tag number(s). It's also used to create EncMode or DecMode. For example, em := EncOptions{...}.EncModeWithTags(ts) or em := EncOptions{...}.EncModeWithSharedTags(ts). This allows every standard API exported by em (like Marshal and NewEncoder) to use the specified tags automatically.

Tag and RawTag can be used to encode/decode a tag number with a Go value, but TagSet is generally recommended.

type TagSet interface {
    // Add adds given tag number(s), content type, and tag options to TagSet.
    Add(opts TagOptions, contentType reflect.Type, num uint64, nestedNum ...uint64) error

    // Remove removes given tag content type from TagSet.
    Remove(contentType reflect.Type)    
}

Tag and RawTag types can also be used to encode/decode tag number with Go value.

type Tag struct {
    Number  uint64
    Content interface{}
}

type RawTag struct {
    Number  uint64
    Content RawMessage
}

See API docs (godoc.org) for more details and more functions. See Usage section for usage and code examples.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Options

Struct tags, decoding options, and encoding options.

Struct Tags

This library supports both "cbor" and "json" key for some (not all) struct tags. If "cbor" and "json" keys are both present for the same field, then "cbor" key will be used.

Key Format Str Scope Description
cbor or json "myName" field Name of field to use such as "myName", etc. like encoding/json.
cbor or json ",omitempty" field Omit (ignore) this field if value is empty, like encoding/json.
cbor or json "-" field Omit (ignore) this field always, like encoding/json.
cbor ",keyasint" field Treat field as an element of CBOR map with specified int as key.
cbor ",toarray" struct Treat each field as an element of CBOR array. This automatically disables "omitempty" and "keyasint" for all fields in the struct.

The "keyasint" struct tag requires an integer key to be specified:

type myStruct struct {
    MyField     int64    `cbor:-1,keyasint,omitempty`
    OurField    string   `cbor:0,keyasint,omitempty`
    FooField    Foo      `cbor:5,keyasint,omitempty`
    BarField    Bar      `cbor:hello,omitempty`
    ...
}

The "toarray" struct tag requires a special field "_" (underscore) to indicate "toarray" applies to the entire struct:

type myStruct struct {
    _           struct{}    `cbor:",toarray"`
    MyField     int64
    OurField    string
    ...
}

Click to expand:

Example Using CBOR Web Tokens

alt text

Decoding Options

DecOptions.TimeTag Description
DecTagIgnored (default) Tag numbers are ignored (if present) for time values.
DecTagOptional Tag numbers are only checked for validity if present for time values.
DecTagRequired Tag numbers must be provided for time values except for CBOR Null and CBOR Undefined.

The following CBOR time values are decoded as Go's "zero time instant":

  • CBOR Null
  • CBOR Undefined
  • CBOR floating-point NaN
  • CBOR floating-point Infinity

Go's time package provides IsZero function, which reports whether t represents "zero time instant"
(January 1, year 1, 00:00:00 UTC).

DecOptions.DupMapKey Description
DupMapKeyQuiet (default) turns off detection of duplicate map keys. It uses a "keep fastest" method by choosing either "keep first" or "keep last" depending on the Go data type.
DupMapKeyEnforcedAPF enforces detection and rejection of duplidate map keys. Decoding stops immediately and returns DupMapKeyError when the first duplicate key is detected. The error includes the duplicate map key and the index number.

DupMapKeyEnforcedAPF uses "Allow Partial Fill" so the destination map or struct can contain some decoded values at the time of error. Users can respond to the DupMapKeyError by discarding the partially filled result if that's required by their protocol.

DecOptions.IndefLength Description
IndefLengthAllowed (default) allow indefinite length data
IndefLengthForbidden forbid indefinite length data
DecOptions.TagsMd Description
TagsAllowed (default) allow CBOR tags (major type 6)
TagsForbidden forbid CBOR tags (major type 6)
DecOptions.MaxNestedLevels Description
32 (default) allowed setting is [4, 256]
DecOptions.MaxArrayElements Description
131072 (default) allowed setting is [16, 2147483647]
DecOptions.MaxMapPairs Description
131072 (default) allowed setting is [16, 2147483647]

Encoding Options

Integers always encode to the shortest form that preserves value. Encoding of other data types and map key sort order are determined by encoding options.

These functions are provided to create and return a modifiable EncOptions struct with predefined settings.

Predefined EncOptions Description
CanonicalEncOptions() Canonical CBOR (RFC 7049 Section 3.9).
CTAP2EncOptions() CTAP2 Canonical CBOR (FIDO2 CTAP2).
PreferredUnsortedEncOptions() Unsorted, encode float64->float32->float16 when values fit, NaN values encoded as float16 0x7e00.
CoreDetEncOptions() PreferredUnsortedEncOptions() + map keys are sorted bytewise lexicographic.

🌱 CoreDetEncOptions() and PreferredUnsortedEncOptions() are subject to change until the draft RFC they used is approved by IETF.

EncOptions.Sort Description
SortNone (default) No sorting for map keys.
SortLengthFirst Length-first map key ordering.
SortBytewiseLexical Bytewise lexicographic map key ordering
SortCanonical (alias) Same as SortLengthFirst (RFC 7049 Section 3.9)
SortCTAP2 (alias) Same as SortBytewiseLexical (CTAP2 Canonical CBOR).
SortCoreDeterministic (alias) Same as SortBytewiseLexical.
EncOptions.Time Description
TimeUnix (default) (seconds) Encode as integer.
TimeUnixMicro (microseconds) Encode as floating-point. ShortestFloat option determines size.
TimeUnixDynamic (seconds or microseconds) Encode as integer if time doesn't have fractional seconds, otherwise encode as floating-point rounded to microseconds.
TimeRFC3339 (seconds) Encode as RFC 3339 formatted string.
TimeRFC3339Nano (nanoseconds) Encode as RFC3339 formatted string.
EncOptions.TimeTag Description
EncTagNone (default) Tag number will not be encoded for time values.
EncTagRequired Tag number (0 or 1) will be encoded unless time value is undefined/zero-instant.

Undefined Time Values

By default, undefined (zero instant) time values will encode as CBOR Null without tag number for both EncTagNone and EncTagRequired. Although CBOR Undefined might be technically more correct for EncTagRequired, CBOR Undefined might not be supported by other generic decoders and it isn't supported by JSON.

Go's time package provides IsZero function, which reports whether t represents the zero time instant, January 1, year 1, 00:00:00 UTC.

Floating-Point Options

Encoder has 3 types of options for floating-point data: ShortestFloatMode, InfConvertMode, and NaNConvertMode.

EncOptions.ShortestFloat Description
ShortestFloatNone (default) No size conversion. Encode float32 and float64 to CBOR floating-point of same bit-size.
ShortestFloat16 Encode float64 -> float32 -> float16 (IEEE 754 binary16) when values fit.

Conversions for infinity and NaN use InfConvert and NaNConvert settings.

EncOptions.InfConvert Description
InfConvertFloat16 (default) Convert +- infinity to float16 since they always preserve value (recommended)
InfConvertNone Don't convert +- infinity to other representations -- used by CTAP2 Canonical CBOR
EncOptions.NaNConvert Description
NaNConvert7e00 (default) Encode to 0xf97e00 (CBOR float16 = 0x7e00) -- used by RFC 7049 Canonical CBOR.
NaNConvertNone Don't convert NaN to other representations -- used by CTAP2 Canonical CBOR.
NaNConvertQuiet Force quiet bit = 1 and use shortest form that preserves NaN payload.
NaNConvertPreserveSignal Convert to smallest form that preserves value (quit bit unmodified and NaN payload preserved).
EncOptions.IndefLength Description
IndefLengthAllowed (default) allow indefinite length data
IndefLengthForbidden forbid indefinite length data
EncOptions.TagsMd Description
TagsAllowed (default) allow CBOR tags (major type 6)
TagsForbidden forbid CBOR tags (major type 6)

Tag Options

TagOptions specifies how encoder and decoder handle tag number registered with TagSet.

TagOptions.DecTag Description
DecTagIgnored (default) Tag numbers are ignored (if present).
DecTagOptional Tag numbers are only checked for validity if present.
DecTagRequired Tag numbers must be provided except for CBOR Null and CBOR Undefined.
TagOptions.EncTag Description
EncTagNone (default) Tag number will not be encoded.
EncTagRequired Tag number will be encoded.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Usage

🛡️ Use Go's io.LimitReader to limit size when decoding very large or indefinite size data.

Functions with identical signatures to encoding/json include:
Marshal, Unmarshal, NewEncoder, NewDecoder, (*Encoder).Encode, (*Decoder).Decode.

Default Mode

If default options are acceptable, package level functions can be used for encoding and decoding.

b, err := cbor.Marshal(v)        // encode v to []byte b

err := cbor.Unmarshal(b, &v)     // decode []byte b to v

encoder := cbor.NewEncoder(w)    // create encoder with io.Writer w

decoder := cbor.NewDecoder(r)    // create decoder with io.Reader r

Modes

If you need to use options or CBOR tags, then you'll want to create a mode.

"Mode" means defined way of encoding or decoding -- it links the standard API to your CBOR options and CBOR tags. This way, you don't pass around options and the API remains identical to encoding/json.

EncMode and DecMode are interfaces created from EncOptions or DecOptions structs.
For example, em, err := cbor.EncOptions{...}.EncMode() or em, err := cbor.CanonicalEncOptions().EncMode().

EncMode and DecMode use immutable options so their behavior won't accidentally change at runtime. Modes are reusable, safe for concurrent use, and allow fast parallelism.

Creating and Using Encoding Modes

EncMode is an interface (API) created from EncOptions struct. EncMode uses immutable options after being created and is safe for concurrent use. For best performance, EncMode should be reused.

// Create EncOptions using either struct literal or a function.
opts := cbor.CanonicalEncOptions()

// If needed, modify opts. For example: opts.Time = cbor.TimeUnix

// Create reusable EncMode interface with immutable options, safe for concurrent use.
em, err := opts.EncMode()   

// Use EncMode like encoding/json, with same function signatures.
b, err := em.Marshal(v)      // encode v to []byte b

encoder := em.NewEncoder(w)  // create encoder with io.Writer w
err := encoder.Encode(v)     // encode v to io.Writer w

Struct Tags (keyasint, toarray, omitempty)

The keyasint, toarray, and omitempty struct tags make it easy to use compact CBOR message formats. Internet standards often use CBOR arrays and CBOR maps with int keys to save space.

alt text

Decoding CWT (CBOR Web Token) using keyasint and toarray struct tags:

// Signed CWT is defined in RFC 8392
type signedCWT struct {
    _           struct{} `cbor:",toarray"`
    Protected   []byte
    Unprotected coseHeader
    Payload     []byte
    Signature   []byte
}

// Part of COSE header definition
type coseHeader struct {
    Alg int    `cbor:"1,keyasint,omitempty"`
    Kid []byte `cbor:"4,keyasint,omitempty"`
    IV  []byte `cbor:"5,keyasint,omitempty"`
}

// data is []byte containing signed CWT

var v signedCWT
if err := cbor.Unmarshal(data, &v); err != nil {
    return err
}

Encoding CWT (CBOR Web Token) using keyasint and toarray struct tags:

// Use signedCWT struct defined in "Decoding CWT" example.

var v signedCWT
...
if data, err := cbor.Marshal(v); err != nil {
    return err
}

Encoding and Decoding CWT (CBOR Web Token) with CBOR Tags

// Use signedCWT struct defined in "Decoding CWT" example.

// Create TagSet (safe for concurrency).
tags := cbor.NewTagSet()
// Register tag COSE_Sign1 18 with signedCWT type.
tags.Add(   
    cbor.TagOptions{EncTag: cbor.EncTagRequired, DecTag: cbor.DecTagRequired}, 
    reflect.TypeOf(signedCWT{}), 
    18)

// Create DecMode with immutable tags.
dm, _ := cbor.DecOptions{}.DecModeWithTags(tags)

// Unmarshal to signedCWT with tag support.
var v signedCWT
if err := dm.Unmarshal(data, &v); err != nil {
    return err
}

// Create EncMode with immutable tags.
em, _ := cbor.EncOptions{}.EncModeWithTags(tags)

// Marshal signedCWT with tag number.
if data, err := cbor.Marshal(v); err != nil {
    return err
}

For more examples, see [examples_test.go](example_test.go).

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Comparisons

Comparisons are between this newer library and a well-known library that had 1,000+ stars before this library was created. Default build settings for each library were used for all comparisons.

This library is safer. Small malicious CBOR messages are rejected quickly before they exhaust system resources.

alt text

This library is smaller. Programs like senmlCat can be 4 MB smaller by switching to this library. Programs using more complex CBOR data types can be 9.2 MB smaller.

alt text

This library is faster for encoding and decoding CBOR Web Token (CWT). However, speed is only one factor and it can vary depending on data types and sizes. Unlike the other library, this one doesn't use Go's unsafe package or code gen.

alt text

This library uses less memory for encoding and decoding CBOR Web Token (CWT) using test data from RFC 8392 A.1.

alt text

Doing your own comparisons is highly recommended. Use your most common message sizes and data types.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Benchmarks

Go structs are faster than maps with string keys:

  • decoding into struct is >28% faster than decoding into map.
  • encoding struct is >35% faster than encoding map.

Go structs with keyasint struct tag are faster than maps with integer keys:

  • decoding into struct is >28% faster than decoding into map.
  • encoding struct is >34% faster than encoding map.

Go structs with toarray struct tag are faster than slice:

  • decoding into struct is >15% faster than decoding into slice.
  • encoding struct is >12% faster than encoding slice.

Doing your own benchmarks is highly recommended. Use your most common message sizes and data types.

See [Benchmarks for fxamacker/cbor](CBOR_BENCHMARKS.md).

Fuzzing and Code Coverage

Over 375 tests must pass on 4 architectures before tagging a release. They include all RFC 7049 examples, bugs found by fuzzing, maliciously crafted CBOR data, and over 87 tests with malformed data.

Code coverage must not fall below 95% when tagging a release. Code coverage is 98.6% (go test -cover) for cbor v2.2 which is among the highest for libraries (in Go) of this type.

Coverage-guided fuzzing must pass 250+ million execs before tagging a release. Fuzzing uses fxamacker/cbor-fuzz. Default corpus has:

Over 1,100 files (corpus) are used for fuzzing because it includes fuzz-generated corpus.

To prevent excessive delays, fuzzing is not restarted for a release if changes are limited to docs and comments.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense

Versions and API Changes

This project uses Semantic Versioning, so the API is always backwards compatible unless the major version number changes.

These functions have signatures identical to encoding/json and they will likely never change even after major new releases:
Marshal, Unmarshal, NewEncoder, NewDecoder, (*Encoder).Encode, and (*Decoder).Decode.

Newly added API documented as "subject to change" are excluded from SemVer.

Newly added API in the master branch that has never been release tagged are excluded from SemVer.

Code of Conduct

This project has adopted the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). Contact faye.github@gmail.com with any questions or comments.

Contributing

Please refer to [How to Contribute](CONTRIBUTING.md).

Security Policy

Security fixes are provided for the latest released version of fxamacker/cbor.

For the full text of the Security Policy, see [SECURITY.md](SECURITY.md).

Disclaimers

Phrases like "no crashes", "doesn't crash", and "is secure" mean there are no known crash bugs in the latest version based on results of unit tests and coverage-guided fuzzing. They don't imply the software is 100% bug-free or 100% invulnerable to all known and unknown attacks.

Please read the license for additional disclaimers and terms.

Special Thanks

Making this library better

  • Stefan Tatschner for using this library in sep, being the 1st to discover my CBOR library, requesting time.Time in issue #1, and submitting this library in a PR to cbor.io on Aug 12, 2019.
  • Yawning Angel for using this library to oasis-core, and requesting BinaryMarshaler in issue #5.
  • Jernej Kos for requesting RawMessage in issue #11 and offering feedback on v2.1 API for CBOR tags.
  • ZenGround0 for using this library in go-filecoin, filing "toarray" bug in issue #129, and requesting
    CBOR BSTR <--> Go array in #133.
  • Keith Randall for fixing Go bugs and providing workarounds so we don't have to wait for new versions of Go.

Help clarifying CBOR RFC 7049 or 7049bis

  • Carsten Bormann for RFC 7049 (CBOR), adding this library to cbor.io, his fast confirmation to my RFC 7049 errata, approving my pull request to 7049bis, and his patience when I misread a line in 7049bis.
  • Laurence Lundblade for his help on the IETF mailing list for 7049bis and for pointing out on a CBORbis issue that CBOR Undefined might be problematic translating to JSON.
  • Jeffrey Yasskin for his help on the IETF mailing list for 7049bis.

Words of encouragement and support

  • Jakob Borg for his words of encouragement about this library at Go Forum. This is especially appreciated in the early stages when there's a lot of rough edges.

License

Copyright © 2019-present Faye Amacker.

fxamacker/cbor is licensed under the MIT License. See [LICENSE](LICENSE) for the full license text.

Quick StartStatusDesign GoalsFeaturesStandardsAPIOptionsUsageFuzzingLicense


*Note that all licence references and agreements mentioned in the cbor README section above are relevant to that project's source code only.