@signalk/nmea0183-signalk
12
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
tkurkisbenderpanaaj
Keywords
nmea0183nmea0183signalksignalkparser
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): SignalK org migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate pipeline origin. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-level CI publishing consolidation; official SignalK GitHub repo confirms legitimate ownership. | ai | |
| phantom-deps | phantom-dep:split | AI (phantom-deps): split is a declared runtime dep used in streaming pipeline; phantom-dep heuristic misses indirect/config usage patterns in this package. | ai | |
| dependencies | unvetted-dep:ggencoder | AI (dependencies): Legitimate dependency for NMEA encoding; stable use across versions of this package. | ai | |
| dependencies | unvetted-dep:@signalk/signalk-schema | AI (dependencies): Same SignalK org dependency; expected and stable for this package. | ai | |
| dependencies | unvetted-dep:@signalk/nmea0183-utilities | AI (dependencies): Same SignalK org utility dependency; expected and stable for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.20.1 | 4 / 15 | |
| 3.20.0 | 4 / 15 | |
| 3.19.2 | 4 / 15 | |
| 3.19.1 | 4 / 14 | |
| 3.19.0 | 4 / 14 | |
| 3.18.0 | 4 / 6 | |
| 3.17.4 | 4 / 6 | |
| 3.17.3 | 5 / 6 | |
| 3.17.2 | 5 / 6 | |
| 3.16.0 | 5 / 6 | |
| 3.15.3 | 5 / 6 | |
| 3.15.2 | 5 / 6 |
v3.20.1
1 finding
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.15.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
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.