@openfin/remote-adapter
Establish intermachine runtime connections using webRTC.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established OpenFin org package; lack of provenance is consistent across all 620 versions. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled bundles; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:openfin-adapter | AI (dependencies): file: dep is a monorepo bundling pattern; openfin-adapter is listed in bundleDependencies and bundled at publish time. | ai | |
| npm-metadata | url-dep:openfin-adapter | AI (npm-metadata): file: path is a monorepo internal dep bundled at publish; not a runtime registry bypass risk. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used inside a Proxy trap handler — standard JS pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:openfin-adapter | AI (phantom-deps): Bundled via bundleDependencies; not directly imported as a module but legitimately included. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 46.100.5 | 3 / 0 | |
| 46.100.4 | 3 / 0 | |
| 46.100.3 | 3 / 0 | |
| 46.100.2 | 3 / 0 | |
| 46.100.1 | 3 / 0 | |
| 45.100.94 | 3 / 0 | |
| 45.100.93 | 3 / 0 | |
| 45.100.92 | 3 / 0 | |
| 45.100.91 | 3 / 0 | |
| 45.100.90 | 3 / 0 | |
| 45.100.89 | 3 / 0 | |
| 45.100.88 | 3 / 0 | |
| 45.100.78 | 3 / 0 | |
| 45.100.76 | 3 / 0 | |
| 45.100.43 | 2 / 0 | |
| 45.100.40 | 2 / 0 | |
| 45.100.39 | 2 / 0 | |
| 44.100.62 | 2 / 0 | |
| 44.100.61 | 2 / 0 | |
| 44.100.60 | 2 / 0 | |
| 44.100.59 | 2 / 0 | |
| 44.100.51 | 2 / 0 | |
| 43.102.1 | 2 / 0 | |
| 43.101.4 | 2 / 0 | |
| 43.101.2 | 2 / 0 | |
| 43.101.1 | 2 / 0 | |
| 43.100.110 | 2 / 0 | |
| 42.103.4 | 2 / 0 | |
| 36.80.9 | 2 / 7 |
v46.100.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v45.100.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v45.100.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v45.100.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v45.100.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v44.100.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.100.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.100.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v44.100.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v44.100.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.102.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.101.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.101.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.101.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.100.110
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (michaelmcoates) than the most recent previously approved version (openfin-ci) on 2025-12-12, but michaelmcoates 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.
v42.103.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.