← Home

@coasys/ad4m-connect

npm

Lib for handling everything needed to setup a connection to a local or remote ad4m-executor

4
Versions
CAL-1.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

leifriksheimlucksusjdeepeefayeedjhweir_coasysjhweir

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package with 116 versions; lack of provenance is consistent across all prior releases. ai
phantom-deps phantom-dep:esbuild-plugin-copy AI (phantom-deps): Build-time plugin referenced in esbuild config scripts, not imported in source — stable false positive. ai
phantom-deps phantom-dep:esbuild-plugin-replace AI (phantom-deps): Build-time plugin referenced in esbuild config scripts, not imported in source — stable false positive. ai
phantom-deps phantom-dep:@undecaf/barcode-detector-polyfill AI (phantom-deps): Barcode polyfill likely loaded dynamically or via config; stable false positive for this package. ai
phantom-deps phantom-dep:@undecaf/zbar-wasm AI (phantom-deps): WASM binary dependency; platform-specific loading pattern explains phantom-dep finding. ai
phantom-deps phantom-dep:auto-bind AI (phantom-deps): Utility likely used indirectly or bundled; stable false positive for this package. ai

Versions (showing 4 of 4)

Version Deps Published
0.12.0 6 / 10
0.11.1 6 / 10
0.11.0 6 / 10
0.10.1 6 / 10

v0.12.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.

v0.11.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.

v0.11.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.

v0.10.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.