← Home

@openfin/node-adapter

npm

See README.md

100
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 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

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Known maintainer manual publish pattern for this package, not a compromise indicator. ai
publish-pattern new-deps-added AI (publish-pattern): lodash is a mainstream, well-audited dependency replacing es-toolkit. ai
provenance publisher-changed AI (provenance): Transition from personal account to GitHub Actions CI is a documented automation pattern for this established OpenFin package. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared runtime dep used implicitly by the bundled output; stable false positive. ai
npm-metadata bundled-binaries AI (npm-metadata): OpenFinRVM.exe is the documented Runtime Version Manager; expected in all OpenFin node-adapter releases. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a type-only dependency; not directly imported at runtime by convention. ai
semgrep semgrep:child-process-spawn AI (semgrep): child_process.spawn is used to launch the OpenFin runtime — core functionality of this adapter package. ai
semgrep semgrep:child-process-import AI (semgrep): child_process import is required for runtime launching; stable pattern across all versions. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get used in a Proxy handler for console.warn interception — benign pattern in this codebase. ai

Versions (showing 100 of 135)

Version Deps Published
46.100.42 5 / 0
46.100.40 5 / 0
46.100.39 5 / 0
46.100.38 5 / 0
46.100.37 5 / 0
46.100.36 5 / 0
46.100.35 5 / 0
46.100.32 5 / 0
46.100.31 5 / 0
46.100.30 5 / 0
46.100.29 5 / 0
46.100.28 5 / 0
46.100.27 5 / 0
46.100.26 5 / 0
46.100.25 5 / 0
46.100.24 5 / 0
46.100.23 5 / 0
46.100.22 5 / 0
46.100.21 5 / 0
46.100.20 5 / 0
46.100.17 5 / 0
46.100.16 5 / 0
46.100.10 5 / 0
46.100.9 5 / 0
46.100.8 5 / 0
46.100.7 5 / 0
46.100.6 5 / 0
46.100.4 5 / 0
46.100.3 5 / 0
46.100.2 5 / 0
46.100.1 5 / 0
45.100.106 5 / 0
45.100.105 5 / 0
45.100.104 5 / 0
45.100.103 5 / 0
45.100.102 5 / 0
45.100.101 5 / 0
45.100.100 5 / 0
45.100.99 5 / 0
45.100.98 5 / 0
45.100.95 5 / 0
45.100.94 5 / 0
45.100.93 5 / 0
45.100.92 5 / 0
45.100.91 5 / 0
45.100.90 5 / 0
45.100.89 5 / 0
45.100.88 5 / 0
45.100.87 5 / 0
45.100.86 5 / 0
45.100.85 5 / 0
45.100.84 5 / 0
45.100.83 5 / 0
45.100.81 5 / 0
45.100.79 5 / 0
45.100.78 5 / 0
45.100.77 5 / 0
45.100.76 5 / 0
45.100.74 5 / 0
45.100.72 5 / 0
45.100.70 5 / 0
45.100.68 5 / 0
45.100.67 5 / 0
45.100.65 5 / 0
45.100.63 5 / 0
45.100.62 5 / 0
45.100.61 5 / 0
45.100.60 5 / 0
45.100.58 5 / 0
45.100.48 5 / 0
45.100.46 5 / 0
45.100.43 4 / 0
45.100.41 4 / 0
45.100.40 4 / 0
45.100.39 4 / 0
45.100.38 4 / 0
45.100.37 4 / 0
45.100.32 4 / 0
45.100.30 4 / 0
45.100.29 4 / 0
45.100.27 4 / 0
45.100.23 4 / 0
45.100.19 4 / 0
45.100.18 4 / 0
44.101.5 5 / 0
44.101.4 5 / 0
44.101.3 5 / 0
44.101.2 5 / 0
44.100.108 4 / 0
44.100.107 4 / 0
44.100.106 4 / 0
44.100.105 4 / 0
44.100.62 4 / 0
44.100.61 4 / 0
44.100.60 4 / 0
44.100.59 4 / 0
44.100.58 4 / 0
44.100.57 4 / 0
44.100.54 4 / 0
44.100.53 4 / 0
Showing 100 of 135 Next page →

v46.100.42

1 finding
LOW No provenance attestation provenance

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

v46.100.40

1 finding
LOW No provenance attestation provenance

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

v46.100.39

1 finding
LOW No provenance attestation provenance

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

v46.100.38

1 finding
LOW No provenance attestation provenance

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

v46.100.37

1 finding
LOW No provenance attestation provenance

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

v46.100.36

1 finding
LOW No provenance attestation provenance

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

v46.100.35

1 finding
LOW No provenance attestation provenance

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

v46.100.32

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: openfin-ci → GitHub Actions (on 2026-07-09) provenance

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

v46.100.31

1 finding
LOW No provenance attestation provenance

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

v46.100.30

1 finding
LOW No provenance attestation provenance

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

v46.100.29

1 finding
LOW No provenance attestation provenance

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

v46.100.28

1 finding
LOW No provenance attestation provenance

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

v46.100.27

1 finding
LOW No provenance attestation provenance

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

v46.100.26

1 finding
LOW No provenance attestation provenance

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

v46.100.25

1 finding
LOW No provenance attestation provenance

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

v45.100.106

1 finding
LOW No provenance attestation provenance

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

v45.100.105

1 finding
LOW No provenance attestation provenance

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

v45.100.104

1 finding
LOW No provenance attestation provenance

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

v45.100.103

1 finding
LOW No provenance attestation provenance

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

v45.100.102

1 finding
LOW No provenance attestation provenance

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

v45.100.101

1 finding
LOW No provenance attestation provenance

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

v45.100.100

1 finding
LOW No provenance attestation provenance

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

v45.100.41

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.

v45.100.40

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.

v45.100.39

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.

v45.100.38

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.

v45.100.37

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.

v45.100.32

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.

v45.100.30

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.

v45.100.29

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.

v45.100.27

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.

v45.100.23

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.

v45.100.19

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.

v45.100.18

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.

v44.101.5

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: connormccafferty.

LOW No provenance attestation provenance

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

INFO Publisher changed: GitHub Actions → connormccafferty (on 2026-06-30, known maintainer) provenance

This version was published by a different npm account (connormccafferty) than the most recent previously approved version (GitHub Actions) on 2026-06-30, but connormccafferty is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v44.100.107

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.

v44.100.106

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.

v44.100.105

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.

v44.100.62

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.

v44.100.61

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.

v44.100.60

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.

v44.100.59

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.

v44.100.58

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.

v44.100.57

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.

v44.100.54

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.

v44.100.53

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.