cbor
Encode and parse data in the Concise Binary Object Representation (CBOR) data format (RFC8949).
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in cbor encoder is used for CBOR-encoded constants (NaN, Infinity). This is core CBOR encoding functionality, not malicious payload hiding. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in map.js is used for canonical sorting of CBOR map keys — legitimate CBOR spec compliance, not obfuscation. | ai |
Versions (showing 51 of 65)
| Version | Deps | Published |
|---|---|---|
| 10.0.12 | 1 / 0 | |
| 10.0.11 | 1 / 0 | |
| 10.0.10 | 1 / 0 | |
| 10.0.9 | 1 / 0 | |
| 10.0.3 | 1 / 0 | |
| 10.0.2 | 1 / 0 | |
| 9.0.2 | 1 / 5 | |
| 9.0.1 | 1 / 5 | |
| 9.0.0 | 1 / 5 | |
| 8.1.0 | 1 / 5 | |
| 8.0.2 | 1 / 5 | |
| 8.0.0 | 1 / 5 | |
| 7.0.6 | 2 / 3 | |
| 7.0.5 | 2 / 3 | |
| 7.0.4 | 2 / 3 | |
| 7.0.3 | 2 / 3 | |
| 7.0.2 | 1 / 3 | |
| 7.0.1 | 1 / 3 | |
| 7.0.0 | 1 / 4 | |
| 6.0.1 | 2 / 8 | |
| 6.0.0 | 2 / 8 | |
| 5.2.0 | 2 / 8 | |
| 5.1.2 | 2 / 8 | |
| 5.1.1 | 2 / 8 | |
| 5.1.0 | 2 / 8 | |
| 5.0.2 | 2 / 10 | |
| 5.0.1 | 2 / 10 | |
| 4.3.0 | 4 / 12 | |
| 4.2.1 | 4 / 12 | |
| 4.2.0 | 4 / 12 | |
| 4.1.5 | 4 / 11 | |
| 4.1.4 | 4 / 10 | |
| 4.1.3 | 4 / 10 | |
| 4.1.2 | 4 / 10 | |
| 4.1.1 | 4 / 10 | |
| 4.1.0 | 4 / 11 | |
| 4.0.0 | 4 / 11 | |
| 3.0.3 | 4 / 11 | |
| 3.0.2 | 4 / 4 | |
| 3.0.0 | 4 / 3 | |
| 2.0.2 | 4 / 3 | |
| 2.0.1 | 4 / 3 | |
| 2.0.0 | 4 / 10 | |
| 1.0.6 | 4 / 13 | |
| 1.0.5 | 4 / 13 | |
| 1.0.4 | 4 / 13 | |
| 1.0.3 | 4 / 16 | |
| 1.0.2 | 4 / 16 | |
| 1.0.1 | 4 / 17 | |
| 0.3.14 | 3 / 17 | |
| 0.3.13 | 3 / 15 |
v10.0.12
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.