@openfin/core
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 | publisher-changed | AI (provenance): Move to GitHub Actions CI publishing is a legitimate automation transition, not compromise. | ai | |
| provenance | missing-githead | AI (provenance): Known maintainer manual publish; no behavioral evidence of tampering. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known TypeScript runtime helper; stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): es-toolkit is a well-established utility library replacing lodash; not a suspicious dependency addition. | ai | |
| source-diff | net-exec-file:out/stub.mjs | AI (source-diff): stub.mjs is the ESM build artifact of the OpenFin SDK; network calls and dynamic execution are part of the SDK's normal IPC/runtime bridge, not malware. | ai | |
| phantom-deps | phantom-dep:openfin-adapter | AI (phantom-deps): Bundled monorepo dep; not directly imported but included via bundleDependencies. | ai | |
| npm-metadata | url-dep:openfin-adapter | AI (npm-metadata): file: dep is a monorepo bundled dependency (listed in bundleDependencies); stable pattern for this package. | ai | |
| dependencies | unvetted-dep:openfin-adapter | AI (dependencies): Monorepo file: reference bundled into the package; not a registry bypass risk. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @openfin/core is a legitimate scoped package from OpenFin, not a typosquat of 'cors'. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type-only dep loaded by convention; phantom-dep finding is expected and benign. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dep used by the OpenFin runtime layer; phantom-dep heuristic is a false positive here. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a proxy/stub pattern in out/stub.js; not obfuscation. | ai |
Versions (showing 51 of 229)
| Version | Deps | Published |
|---|---|---|
| 46.100.45 | 5 / 0 | |
| 46.100.44 | 5 / 0 | |
| 46.100.43 | 5 / 0 | |
| 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.18 | 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.5 | 5 / 0 | |
| 46.100.4 | 5 / 0 | |
| 46.100.3 | 5 / 0 | |
| 46.100.2 | 5 / 0 | |
| 46.100.1 | 5 / 0 | |
| 45.100.107 | 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 |
v46.100.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.30
2 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.29
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.28
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.27
2 findingsThis version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.26
2 findingsThis version was published by a different npm account than previous versions on 2026-06-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.25
2 findingsThis version was published by a different npm account than previous versions on 2026-06-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.107
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
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.103
2 findingsThis version was published by a different npm account than previous versions on 2026-07-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.102
2 findingsThis version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.101
2 findingsThis version was published by a different npm account than previous versions on 2026-06-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.100
2 findingsThis version was published by a different npm account than previous versions on 2026-06-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.