@openfin/node-adapter SEE LICENSE IN LICENSE.md 35 versions

@openfin/node-adapter

npm

See README.md

35

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.

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

Versions (showing 35 of 135)

Version	Deps	Published
44.100.52	4 / 0	2025-11-25
44.100.51	4 / 0	2025-11-24
44.100.50	4 / 0	2025-11-21
44.100.49	4 / 0	2025-11-20
44.100.48	4 / 0	2025-11-19
44.100.47	4 / 0	2025-11-18
44.100.46	4 / 0	2025-11-17
44.100.40	4 / 0	2025-11-07
44.100.39	4 / 0	2025-11-07
44.100.36	4 / 0	2025-11-04
44.100.34	4 / 0	2025-10-31
43.104.1	5 / 0	2026-05-26
43.103.3	4 / 0	2026-04-03
43.103.2	4 / 0	2026-03-27
43.102.2	4 / 0	2026-03-06
43.102.1	4 / 0	2026-03-06
43.101.4	4 / 0	2026-02-10
43.101.2	4 / 0	2026-01-12
43.101.1	4 / 0	2026-01-02
43.100.111	4 / 0	2025-12-18
43.100.110	4 / 0	2025-12-12
43.100.109	4 / 0	2025-12-10
43.100.106	4 / 0	2025-12-03
43.100.105	4 / 0	2025-11-21
43.100.104	4 / 0	2025-11-19
43.100.103	4 / 0	2025-11-18
43.100.102	4 / 0	2025-11-14
43.100.101	4 / 0	2025-11-12
43.100.100	4 / 0	2025-10-31
42.103.4	4 / 0	2026-01-12
42.103.3	4 / 0	2025-12-18
42.103.2	4 / 0	2025-11-21
42.103.1	4 / 0	2025-11-07
40.105.12	5 / 0	2026-07-09
40.105.11	5 / 0	2026-07-09

v44.100.52

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

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

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

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

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

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

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

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

v44.100.36

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

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.

v43.103.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.

v43.102.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.

v43.102.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.

v43.101.4

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.

v43.101.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.

v43.101.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.

v43.100.111

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.

v43.100.110

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.

v43.100.109

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.

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

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

v43.100.104

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.

v43.100.103

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.

v43.100.102

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.

v43.100.101

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.

v43.100.100

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.

v42.103.4

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.

v42.103.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.

v42.103.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.

v40.105.12

1 finding

LOW No provenance attestation provenance

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

v40.105.11

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: openfin-ci.

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 → openfin-ci (on 2026-07-09, known maintainer) provenance

This version was published by a different npm account (openfin-ci) than the most recent previously approved version (GitHub Actions) on 2026-07-09, but openfin-ci 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.