← Home

@signalk/course-provider

npm Repository Homepage

Course data provider plugin for SignalK Server.

16
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

tkurkisbenderpanaaj

Keywords

signalk-node-server-pluginsignalk-category-utilitysignalksignalk-min-api-version:2

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Established package with clean history; missing gitHead reflects CI tooling change, not takeover signal. ai
publish-pattern dormant-publish AI (publish-pattern): Known SignalK plugin with established GitHub org; dormancy consistent with low-maintenance open source, not takeover indicators. ai
dependencies unvetted-dep:@signalk/server-api AI (dependencies): First-party SignalK API package; expected dependency for all SignalK server plugins. ai

Versions (showing 16 of 16)

Version Deps Published
1.4.0 2 / 14
1.3.0 2 / 14
1.2.7 2 / 6
1.2.6 2 / 6
1.2.5 2 / 6
1.2.4 2 / 4
1.2.3 2 / 4
1.2.2 2 / 4
1.2.1 2 / 4
1.2.0 1 / 5
1.1.1 1 / 5
1.1.0 1 / 5
1.0.3 1 / 5
1.0.2 1 / 5
1.0.1 1 / 5
1.0.0 1 / 5

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

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.

v1.0.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.

v1.0.1

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.

v1.0.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.