@openfin/ui-library SEE LICENSE IN LICENSE.MD 42 versions

@openfin/ui-library

npm Repository Homepage

OpenFin UI Component Library

42

Versions

SEE LICENSE IN LICENSE.MD

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

openfincolinhuopenfinbrandonpierrebaizenoyangundaymichaelmcoatesalan15008imansurijohnmandia-openfinrdepenatgoc99wenjuncheharsimran.openfin.singhmichal-pichlinski-hereluiemiliolicui3936connormccaffertyadam.salandopenfin-cichrishobsonexperorichbrowne-openfinazizyokhzhi0209openfin-gavinoblargnewaz.sharifandy.westacottshahossaineugeneross-openfingouthamcopenfin-jeffsakibahmadmanamiuedaxyopenfinhannahmcmillensmocarskidavidcoxon-ofdhilan__tomasz__galim.kaudinovife-dev1gallak-openfineheyderelliott.burrmjoslingyoge-openfinnil.ffejhina-khalideoyewobiyongji.chenmarek_openfinjmransegnolaameet-openfinrutu-bmichalzzopenfin-johansandrewche3openfin-ci-ghahkjeffersongarcia25tpatek17cezary_openfinoliviatarsiache40abanda11nicknewman-herericardo.martini-here.io

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/theme.js	AI (source-diff): Minified webpack bundle output, not true obfuscation; matches new theme/tinycolor2 feature.	ai	2026/07/16
phantom-deps	phantom-dep:lodash.merge	AI (phantom-deps): Used in config, false positive pattern for build-time deps.	ai	2026/07/16
phantom-deps	phantom-dep:focus-trap-react	AI (phantom-deps): Used in config, false positive pattern for build-time deps.	ai	2026/07/16
phantom-deps	phantom-dep:require-from-string	AI (phantom-deps): Used in config, false positive pattern for build-time deps.	ai	2026/07/16

Versions (showing 42 of 42)

Version	Deps	Published
0.31.3	4 / 57	2025-09-29
0.31.2	4 / 57	2025-09-29
0.31.1	4 / 57	2025-09-14
0.31.0	4 / 57	2025-09-12
0.30.21	4 / 51	2025-08-21
0.30.20	4 / 51	2025-08-13
0.30.19	4 / 51	2025-08-08
0.30.18	4 / 51	2025-07-17
0.30.17	4 / 51	2025-07-10
0.30.16	4 / 51	2025-07-10
0.30.15	4 / 51	2025-07-03
0.30.14	4 / 51	2025-07-01
0.30.13	4 / 51	2025-06-27
0.30.12	4 / 51	2025-06-25
0.30.11	4 / 51	2025-06-20
0.30.10	4 / 51	2025-06-12
0.30.9	4 / 51	2025-06-06
0.30.8	4 / 51	2025-05-28
0.30.7	4 / 51	2025-05-22
0.30.6	4 / 51	2025-05-12
0.30.5	4 / 51	2025-04-24
0.30.4	4 / 51	2025-04-08
0.30.3	4 / 51	2025-04-03
0.30.2	4 / 51	2025-04-02
0.30.1	4 / 51	2025-04-01
0.30.0	4 / 51	2025-03-27
0.29.1	4 / 51	2025-03-13
0.29.0	4 / 51	2025-01-29
0.28.1	0 / 53	2025-01-24
0.28.0	0 / 52	2025-01-22
0.27.5	0 / 52	2024-11-15
0.27.4	0 / 52	2024-11-12
0.27.3	0 / 52	2024-11-12
0.27.2	0 / 52	2024-11-07
0.27.0	0 / 52	2024-10-09
0.26.1	0 / 52	2024-06-27
0.26.0	0 / 52	2024-06-21
0.25.4	0 / 52	2024-06-12
0.25.3	0 / 51	2024-05-30
0.25.2	0 / 51	2024-05-29
0.25.1	0 / 51	2024-05-28
0.25.0	0 / 51	2024-05-23

v0.31.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.31.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.31.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.31.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.9

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: openfin-ci → openfinbrandon (on 2025-06-06, known maintainer) provenance

This version was published by a different npm account (openfinbrandon) than the most recent previously approved version (openfin-ci) on 2025-06-06, but openfinbrandon 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.

v0.30.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.5

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.4

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.3

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.2

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.1

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.0

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.1

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.0

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.28.1

2 findings

HIGH New obfuscated file: dist/theme.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.26.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.