borc
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): borc is a well-known CBOR serialization library, not a typosquat of cors. The name similarity is coincidental; completely different domain and functionality. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex-encoded buffers are CBOR spec constants for NaN/Infinity IEEE 754 half-precision floats. Standard practice for a binary serialization library; not malicious. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 7 / 6 | |
| 2.1.2 | 7 / 8 | |
| 2.1.1 | 5 / 7 | |
| 2.1.0 | 5 / 7 | |
| 2.0.4 | 4 / 7 | |
| 2.0.3 | 4 / 7 | |
| 2.0.2 | 4 / 5 | |
| 2.0.1 | 4 / 5 | |
| 2.0.0 | 4 / 5 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.