@openfin/workspace
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in minified bundle of a mature SDK; consistent with template/parser internals, not a novel injection risk. | ai | |
| phantom-deps | phantom-dep:lodash.debounce | AI (phantom-deps): Bundled package; declared dep may be consumed indirectly or tree-shaken; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Same as lodash.debounce — bundled SDK pattern, stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Long-established OpenFin SDK published via GitHub Actions; lack of Sigstore provenance is consistent across all versions. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 45.0.6 | 8 / 0 | |
| 45.0.5 | 8 / 0 | |
| 45.0.4 | 8 / 0 | |
| 45.0.3 | 8 / 0 | |
| 45.0.2 | 8 / 0 | |
| 45.0.1 | 8 / 0 | |
| 45.0.0 | 8 / 0 | |
| 24.1.5 | 8 / 0 | |
| 24.1.4 | 8 / 0 | |
| 24.1.3 | 8 / 0 | |
| 24.1.2 | 8 / 0 | |
| 24.1.1 | 8 / 0 | |
| 24.0.14 | 8 / 0 | |
| 24.0.13 | 8 / 0 | |
| 24.0.12 | 8 / 0 | |
| 24.0.11 | 8 / 0 | |
| 24.0.10 | 8 / 0 | |
| 24.0.9 | 8 / 0 | |
| 24.0.8 | 8 / 0 | |
| 24.0.7 | 8 / 0 | |
| 24.0.6 | 8 / 0 | |
| 23.2.18 | 8 / 0 | |
| 23.2.17 | 8 / 0 | |
| 23.2.16 | 8 / 0 | |
| 23.0.22 | 7 / 0 | |
| 23.0.21 | 7 / 0 | |
| 23.0.1 | 7 / 0 | |
| 23.0.0 | 7 / 0 | |
| 22.5.21 | 7 / 0 | |
| 22.5.20 | 7 / 0 | |
| 22.4.3 | 7 / 0 | |
| 22.3.100 | 7 / 0 | |
| 22.3.39 | 7 / 0 | |
| 22.3.38 | 7 / 0 | |
| 22.3.34 | 7 / 0 | |
| 22.3.28 | 7 / 0 | |
| 22.3.27 | 7 / 0 | |
| 22.3.26 | 7 / 0 |
v45.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.3.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.