@openfin/web-utils
Internal only util library for utilities shared by web-interop, web-layouts and mobile shell.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped @openfin org package; sparse metadata is a style choice, not a spam indicator for this established publisher. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dependency; phantom-dep heuristic fires but uuid is legitimately used in this package. | ai |
Versions (showing 100 of 470)
| Version | Deps | Published |
|---|---|---|
| 0.43.49 | 1 / 0 | |
| 0.43.48 | 1 / 0 | |
| 0.43.46 | 1 / 0 | |
| 0.43.44 | 1 / 0 | |
| 0.43.40 | 1 / 0 | |
| 0.43.39 | 1 / 0 | |
| 0.43.38 | 1 / 0 | |
| 0.43.37 | 1 / 0 | |
| 0.43.36 | 1 / 0 | |
| 0.43.35 | 1 / 0 | |
| 0.43.34 | 1 / 0 | |
| 0.43.31 | 1 / 0 | |
| 0.43.28 | 1 / 0 | |
| 0.43.27 | 1 / 0 | |
| 0.43.26 | 1 / 0 | |
| 0.43.25 | 1 / 0 | |
| 0.43.22 | 1 / 0 | |
| 0.43.21 | 1 / 0 | |
| 0.43.19 | 1 / 0 | |
| 0.43.16 | 1 / 0 | |
| 0.43.14 | 1 / 0 | |
| 0.43.10 | 1 / 0 | |
| 0.43.9 | 1 / 0 | |
| 0.43.8 | 1 / 0 | |
| 0.43.7 | 1 / 0 | |
| 0.43.5 | 1 / 0 | |
| 0.43.4 | 1 / 0 | |
| 0.43.2 | 1 / 0 | |
| 0.42.114 | 1 / 0 | |
| 0.42.113 | 1 / 0 | |
| 0.42.112 | 1 / 0 | |
| 0.42.111 | 1 / 0 | |
| 0.42.110 | 1 / 0 | |
| 0.42.108 | 1 / 0 | |
| 0.42.107 | 1 / 0 | |
| 0.42.106 | 1 / 0 | |
| 0.42.105 | 1 / 0 | |
| 0.42.104 | 1 / 0 | |
| 0.42.103 | 1 / 0 | |
| 0.42.102 | 1 / 0 | |
| 0.42.101 | 1 / 0 | |
| 0.42.99 | 1 / 0 | |
| 0.42.98 | 1 / 0 | |
| 0.42.97 | 1 / 0 | |
| 0.42.96 | 1 / 0 | |
| 0.42.95 | 1 / 0 | |
| 0.42.94 | 1 / 0 | |
| 0.42.93 | 1 / 0 | |
| 0.42.92 | 1 / 0 | |
| 0.42.91 | 1 / 0 | |
| 0.42.90 | 1 / 0 | |
| 0.42.89 | 1 / 0 | |
| 0.42.87 | 1 / 0 | |
| 0.42.86 | 1 / 0 | |
| 0.42.85 | 1 / 0 | |
| 0.42.84 | 1 / 0 | |
| 0.42.83 | 1 / 0 | |
| 0.42.81 | 1 / 0 | |
| 0.42.80 | 1 / 0 | |
| 0.42.79 | 1 / 0 | |
| 0.42.78 | 1 / 0 | |
| 0.42.76 | 1 / 0 | |
| 0.42.73 | 1 / 0 | |
| 0.42.72 | 1 / 0 | |
| 0.42.71 | 1 / 0 | |
| 0.42.70 | 1 / 0 | |
| 0.42.68 | 1 / 0 | |
| 0.42.67 | 1 / 0 | |
| 0.42.66 | 1 / 0 | |
| 0.42.65 | 1 / 0 | |
| 0.42.64 | 1 / 0 | |
| 0.42.62 | 1 / 0 | |
| 0.42.59 | 1 / 0 | |
| 0.42.57 | 1 / 0 | |
| 0.42.56 | 1 / 0 | |
| 0.42.55 | 1 / 0 | |
| 0.42.54 | 1 / 0 | |
| 0.42.53 | 1 / 0 | |
| 0.42.50 | 1 / 0 | |
| 0.42.49 | 1 / 0 | |
| 0.42.48 | 1 / 0 | |
| 0.42.47 | 1 / 0 | |
| 0.42.46 | 1 / 0 | |
| 0.42.44 | 1 / 0 | |
| 0.42.40 | 1 / 0 | |
| 0.42.39 | 1 / 0 | |
| 0.42.38 | 1 / 0 | |
| 0.42.36 | 1 / 0 | |
| 0.42.32 | 1 / 0 | |
| 0.42.31 | 1 / 0 | |
| 0.42.30 | 1 / 0 | |
| 0.42.29 | 1 / 0 | |
| 0.42.28 | 1 / 0 | |
| 0.42.27 | 1 / 0 | |
| 0.42.26 | 1 / 0 | |
| 0.42.25 | 1 / 0 | |
| 0.42.24 | 1 / 0 | |
| 0.42.23 | 1 / 0 | |
| 0.42.22 | 1 / 0 | |
| 0.42.21 | 1 / 0 |
v0.42.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.