@openfin/node-adapter
See README.md
Supply chain provenance
Status for the latest visible version.
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
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 | |
| 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 51 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 |
v46.100.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.32
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.