← Home

@interopio/core

npm Homepage

IOConnect core library

30
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, so a manually published version cannot be tied back to a reviewed commit.

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
publish-pattern new-deps-added AI (publish-pattern): Added deps are established, widely-used utility packages, not suspicious. ai
provenance publisher-changed AI (provenance): Move to GitHub Actions CI publishing is a legitimate transition for this org-owned scoped package. ai
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:lodash.clonedeep AI (phantom-deps): lodash.clonedeep is a declared runtime dep; phantom-dep heuristic misfires on bundled/indirect usage. 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

Versions (showing 30 of 30)

Version Deps Published
6.10.6 6 / 30
6.10.5 6 / 30
6.10.4 6 / 30
6.10.2 6 / 30
6.10.1 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.1 2 / 0
6.7.0 2 / 0
6.6.0 2 / 0
6.5.2 2 / 0
6.5.1 2 / 0
6.5.0 2 / 0
6.4.3 2 / 0
6.4.2 2 / 0
6.4.1 2 / 0
6.4.0 2 / 0
6.3.5 2 / 0
6.3.4 2 / 0
6.3.3 2 / 0
6.3.2 2 / 0
6.3.1 2 / 0
6.3.0 1 / 0
6.2.3 1 / 0
6.2.2 0 / 0

v6.10.2

2 findings
HIGH Publisher changed: trendo7 → GitHub Actions (on 2026-04-20) provenance

This version was published by a different npm account than previous versions on 2026-04-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v6.10.1

2 findings
HIGH Publisher changed: trendo7 → GitHub Actions (on 2026-04-16) provenance

This version was published by a different npm account than previous versions on 2026-04-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v6.7.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: flashd2n → trendo7 (on 2025-10-30) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-30. This could indicate a legitimate maintainer transition or an account compromise.

v6.5.2

1 finding
LOW No provenance attestation provenance

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

v6.5.1

1 finding
LOW No provenance attestation provenance

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

v6.5.0

1 finding
LOW No provenance attestation provenance

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

v6.4.3

1 finding
LOW No provenance attestation provenance

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

v6.4.2

1 finding
LOW No provenance attestation provenance

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

v6.4.1

1 finding
LOW No provenance attestation provenance

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

v6.4.0

1 finding
LOW No provenance attestation provenance

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

v6.3.5

1 finding
LOW No provenance attestation provenance

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

v6.3.4

1 finding
LOW No provenance attestation provenance

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

v6.3.3

1 finding
LOW No provenance attestation provenance

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

v6.3.2

1 finding
LOW No provenance attestation provenance

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

v6.3.1

1 finding
LOW No provenance attestation provenance

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

v6.3.0

1 finding
LOW No provenance attestation provenance

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

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