← Home

@interopio/core

npm Homepage

IOConnect core library

11
Versions
MIT
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

smateevtsachevthorsentstbozovhristo-kolev-interopioppetkowgdavidkovflashd2nstaaflandy.gardnerkiril.popovmitk0936trendo7

Keywords

glueglue42desktopinteropcontextioconnectinterop.ioio.connect desktop

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:decoder-validate AI (dependencies): Stable dependency present across multiple versions of this established package; no malicious indicators. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped @interopio package; 'core' is the package's own name, not a typo of 'cors'. Stable false positive. ai
phantom-deps phantom-dep:nanoid AI (phantom-deps): nanoid is a declared runtime dep; phantom-dep heuristic misfires on bundled/indirect usage. ai
phantom-deps phantom-dep:decoder-validate AI (phantom-deps): decoder-validate is a declared runtime dep; phantom-dep heuristic misfires on bundled/indirect usage. ai
phantom-deps phantom-dep:lodash.clonedeep AI (phantom-deps): lodash.clonedeep is a declared runtime dep; phantom-dep heuristic misfires on bundled/indirect usage. ai

Versions (showing 11 of 11)

Version Deps Published
6.10.5 6 / 30
6.10.4 6 / 30
6.10.0 3 / 0
6.9.1 3 / 0
6.9.0 3 / 0
6.8.1 2 / 0
6.8.0 2 / 0
6.7.3 2 / 0
6.7.2 2 / 0
6.7.0 2 / 0
6.6.0 2 / 0

v6.10.5

1 finding
LOW No provenance attestation provenance

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

v6.10.0

1 finding
LOW No provenance attestation provenance

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

v6.9.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.

v6.9.0

1 finding
LOW No provenance attestation provenance

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

v6.8.1

1 finding
LOW No provenance attestation provenance

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

v6.8.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.

v6.7.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.

v6.7.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.

v6.7.0

1 finding
LOW No provenance attestation provenance

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

v6.6.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.