@signalk/streams
Utilities for handling streams of Signal K data
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:child-process-import | AI (semgrep): execute.js intentionally spawns shell commands for GPS/NMEA/serial stream processing; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@signalk/signalk-schema | AI (phantom-deps): Same org scope; declared as dep even if not directly imported — likely used transitively or conditionally. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is explicitly declared in package.json dependencies; phantom-dep heuristic misfires here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.6.0 | 12 / 0 | |
| 6.5.0 | 12 / 0 | |
| 6.4.0 | 12 / 0 | |
| 6.3.0 | 12 / 0 | |
| 6.0.0 | 13 / 0 | |
| 5.1.4 | 13 / 0 | |
| 5.1.3 | 13 / 0 |
v6.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sbender) than the most recent previously approved version (tkurki) on 2025-12-27, but sbender is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.