← Home

@openfin/cloud-interop-core-api

npm

This package contains the core interop library that handles all interactions with the HERE Cloud Interop Service.

8
Versions
SEE LICENSE IN LICENSE.md
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

openfincolinhuopenfinbrandonpierrebaizenoyangundaymichaelmcoatesalan15008imansurijohnmandia-openfinrdepenatgoc99wenjuncheharsimran.openfin.singhmichal-pichlinski-hereluiemiliolicui3936connormccaffertyopenfin-cichrishobsonexperoliangliu-hererichbrowne-openfinazizyokhzhi0209openfin-gavinoblargnewaz.sharifandy.westacottshahossaineugeneross-openfingouthamcopenfin-jeffsakibahmadmanamiuedaxyopenfinhannahmcmillensmocarskidavidcoxon-ofdhilan__tomasz__galim.kaudinovife-dev1gallak-openfineheyderelliott.burrmjoslingyoge-openfinhina-khalidcrom83eoyewobiyongji.chenmarek_openfinjmransegnolaameet-openfinrutu-bmichalzzopenfin-johansandrewche3openfin-ci-ghuday.guntupalliache40ahkjeffersongarcia25tpatek17cezary_openfinoliviatarsinicknewman-herericardo.martini-here.io

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is used for JWT payload parsing — standard, non-malicious pattern stable across this package's versions. ai
publish-pattern rapid-publish AI (publish-pattern): High-frequency automated CI publishing is the norm for this package (1068 versions); rapid publish is expected behavior. ai

Versions (showing 8 of 8)

Version Deps Published
13.0.2 2 / 0
13.0.1 2 / 0
13.0.0 2 / 0
12.0.2 2 / 0
12.0.1 2 / 0
12.0.0 2 / 0
11.0.0 2 / 0
10.0.0 2 / 0

v13.0.2

1 finding
LOW No provenance attestation provenance

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

v13.0.1

1 finding
LOW No provenance attestation provenance

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

v13.0.0

1 finding
LOW No provenance attestation provenance

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

v12.0.2

1 finding
LOW No provenance attestation provenance

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

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

v11.0.0

1 finding
LOW No provenance attestation provenance

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

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