@foxglove/cdr — Greenflagged

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

foxglovebotamacneil

Keywords

cdrddsrtpsomgserializationdeserializationserderos2

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/CdrWriter.test.js	AI (source-diff): Same tf2_msgs/TFMessage hex fixture used in writer tests; benign test data.	ai	2026/05/26
source-diff	encoded-string-file:src/CdrWriter.test.ts	AI (source-diff): Same hex fixture in TypeScript source; benign test data.	ai	2026/05/26
provenance	publisher-changed	AI (provenance): Transition to GitHub Actions publisher with SLSA provenance attestation is a legitimate CI/CD migration.	ai	2026/05/26
source-diff	encoded-string-file:dist/CdrReader.test.js	AI (source-diff): Hex string is a ROS2 CDR binary test fixture with fully annotated field assertions; not obfuscation.	ai	2026/05/26
source-diff	encoded-string-file:src/CdrReader.test.ts	AI (source-diff): Same hex fixture in TypeScript source; benign test data.	ai	2026/05/26
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding is in test files only, decoding known ROS2 message fixtures — not a runtime payload risk.	ai	2026/05/19
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped @foxglove/cdr is a CDR serialization lib; no plausible typosquat relationship to 'cors'.	ai	2026/05/19

Versions (showing 3 of 3)

Version	Deps	Published
3.5.1	0 / 16	2026-05-25
3.5.0	0 / 16	2025-08-28
3.4.0	0 / 16	2025-07-16

v3.5.1

6 findings

HIGH Publisher changed: foxglovebot → GitHub Actions (on 2026-05-25) provenance

This version was published by a different npm account than previous versions on 2026-05-25. This could indicate a legitimate maintainer transition or an account compromise.

HIGH Long encoded string in modified file: dist/CdrReader.test.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/CdrWriter.test.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: src/CdrReader.test.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: src/CdrWriter.test.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.